You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/05/24 00:52:41 UTC
[jira] Created: (MNG-2317) Provided scope dependencies are based in
target app server, current approach doesn't work very well
Provided scope dependencies are based in target app server, current approach doesn't work very well
---------------------------------------------------------------------------------------------------
Key: MNG-2317
URL: http://jira.codehaus.org/browse/MNG-2317
Project: Maven 2
Type: New Feature
Components: Dependencies
Versions: 2.0.4
Reporter: Carlos Sanchez
Fix For: 2.1
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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2317) Provided scope dependencies are based
in target app server, current approach doesn't work very well
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2317?page=comments#action_75572 ]
Jason van Zyl commented on MNG-2317:
------------------------------------
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.
> Provided scope dependencies are based in target app server, current approach doesn't work very well
> ---------------------------------------------------------------------------------------------------
>
> Key: MNG-2317
> URL: http://jira.codehaus.org/browse/MNG-2317
> Project: Maven 2
> Issue Type: New Feature
> Components: Dependencies
> Affects Versions: 2.0.4
> Reporter: Carlos Sanchez
> Fix For: 2.1
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2317) Provided scope dependencies are based in
target app server, current approach doesn't work very well
Posted by "Milos Kleint (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2317?page=all ]
Milos Kleint updated MNG-2317:
------------------------------
Attachment: nbwebapproject.zip
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.
> Provided scope dependencies are based in target app server, current approach doesn't work very well
> ---------------------------------------------------------------------------------------------------
>
> Key: MNG-2317
> URL: http://jira.codehaus.org/browse/MNG-2317
> Project: Maven 2
> Issue Type: New Feature
> Components: Dependencies
> Affects Versions: 2.0.4
> Reporter: Carlos Sanchez
> Fix For: 2.1
>
> Attachments: nbwebapproject.zip
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2317) Provided scope dependencies are based in
target app server, current approach doesn't work very well
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2317?page=all ]
Carlos Sanchez updated MNG-2317:
--------------------------------
Fix Version: 2.1
> Provided scope dependencies are based in target app server, current approach doesn't work very well
> ---------------------------------------------------------------------------------------------------
>
> Key: MNG-2317
> URL: http://jira.codehaus.org/browse/MNG-2317
> Project: Maven 2
> Type: New Feature
> Components: Dependencies
> Versions: 2.0.4
> Reporter: Carlos Sanchez
> Fix For: 2.1
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira