Maven
  1. Maven
  2. MNG-2317

Provided scope dependencies are based in target app server, current approach doesn't work very well

    Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Incomplete
    • Affects Version/s: 2.0.4
    • Fix Version/s: None
    • Component/s: Dependencies
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      1

      Description

      We'd need a mechanism for the user to set the target app server for stuff like wars, ears,...
      Maybe a plugin, maybe a core feature, that would iterate through dependencies and set scope as "provided" depending on the filter

      A filter can be an xml file listing the dependencies that have to be provided (grop+artifact ?+version?)
      we can provide a set of predefined filters like tomcat4, tomcat5, geronimo,... and the user would be able to add new ones

        Issue Links

          Activity

          Hide
          Jason van Zyl added a comment -

          We should probably get Vincent to look at this and see if he has done anything like this in Cargo. But basically this looks like ApplicationServerToolChain and ApplicationServerToolChainAware.

          Show
          Jason van Zyl added a comment - We should probably get Vincent to look at this and see if he has done anything like this in Cargo. But basically this looks like ApplicationServerToolChain and ApplicationServerToolChainAware.
          Hide
          Milos Kleint added a comment -

          a zip of a sample netbeans project. The way it works is following.
          important files are nbproject/project.properties which is shareable in cvs/svn and nbproject/private/private.properties which is not shareable.
          project.properties contains just the "j2ee.server.type" token that designates if it's a jboss or tomcat or else.
          private.properties has the actual instance of that type for this particular user in the property j2ee.server.instance
          on top of that it also stores the j2ee.platform.classpath property with jars in the app server and puts them on classpath for compilation etc. if the user doesn't have these private props on opening the project he's prompted for it. the IDE is also able to default to server of the same type if defined.

          Show
          Milos Kleint added a comment - a zip of a sample netbeans project. The way it works is following. important files are nbproject/project.properties which is shareable in cvs/svn and nbproject/private/private.properties which is not shareable. project.properties contains just the "j2ee.server.type" token that designates if it's a jboss or tomcat or else. private.properties has the actual instance of that type for this particular user in the property j2ee.server.instance on top of that it also stores the j2ee.platform.classpath property with jars in the app server and puts them on classpath for compilation etc. if the user doesn't have these private props on opening the project he's prompted for it. the IDE is also able to default to server of the same type if defined.
          Show
          Jason van Zyl added a comment - Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
          Hide
          Jason van Zyl added a comment -

          Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

          Show
          Jason van Zyl added a comment - Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

            People

            • Assignee:
              Unassigned
              Reporter:
              Carlos Sanchez
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: