[jira] Commented: (MPIR-106) Regression in 2.1-SNAPSHOT, the Project Dependencies and the Project Transitive Dependencies are the same
[ http://jira.codehaus.org/browse/MPIR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140883#action_140883 ] Arnaud commented on MPIR-106: - So the probleme is in maven-dependency-tree ? But in his JIRA there are no ticket open for this probleme . http://jira.codehaus.org/browse/MDEP/component/12849 I can open it ? > Regression in 2.1-SNAPSHOT, the Project Dependencies and the Project > Transitive Dependencies are the same > --- > > Key: MPIR-106 > URL: http://jira.codehaus.org/browse/MPIR-106 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.1 > Environment: Windows, Maven 2.08, Project Info Reports Plugin > 2.1-SNAPSHOT >Reporter: Arnaud > Fix For: 2.1 > > > In the 2.0.1, in the "Project Dependencies " we find only the direct > dependency, and in the "Project Transitive Dependencies" we find all > dependency (direct and transitive). > in 2.1-SNAPSHOT, both report are same. Then, in Project Dependencies we > find the transitive dependency too. -- 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] Created: (MCHANGES-113) Allow configuration of announcement parameters from command line
Allow configuration of announcement parameters from command line Key: MCHANGES-113 URL: http://jira.codehaus.org/browse/MCHANGES-113 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Affects Versions: 2.0 Reporter: Dennis Lundberg If you use only the announcement functions of the Changes Plugin you might not have it configured in your POM. So you need a way to configure it from the command line when generating the announcement after the release is done. For example the maxEntries parameter might need to be changed if there are lots of issues fixed. -- 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: (MECLIPSE-459) missing artifact references with pde mode enabled
[
http://jira.codehaus.org/browse/MECLIPSE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140899#action_140899
]
Benjamin Voigt commented on MECLIPSE-459:
-
Ok, after some investigation I found that this problem seems to be caused by
two factors:
1. my project has pde enabled
2. the specific dependencies not working are osgi bundles.
This seems to be a bad combination as we have the following in the
EclipseClasspathWriter Class:
...
if ( config.isPde() && ( dep.isProvided() ||
dep.isOsgiBundle() ) )
{
return;
...(line 415)
Thus, not adding for example, jetty 6.1.10 (or any of the above mentioned
dependencies) to the classpath file.
Now my problem is that I neither understand why this is nor what I can do to
add these dependencies to my project.
I am thankful for any suggestions
> missing artifact references with pde mode enabled
> -
>
> Key: MECLIPSE-459
> URL: http://jira.codehaus.org/browse/MECLIPSE-459
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path, PDE
> support
>Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.5.1
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_11
> OS name: "linux" version: "2.6.15-51-686" arch: "i386" Family: "unix"
>Reporter: Benjamin Voigt
>Priority: Critical
> Attachments: pde_dep_missing.zip
>
>
> Some artifacts are not referenced after executing mvn eclipse:eclipse and
> having pde mode enabled. The strange thing is, that this does only happen for
> particluar versions of an artifact.
> Two artifacts that I found with this problem are jetty (org.mortbay.jetty)
> and slf4j-log4j12 (org.slf4j-log4j12). Jetty versions beyond 6.1.5 work with
> pde enabled, higher versions do not. Same for slf4j-log4j12 versions =< 1.1.0.
> Attached is an example project demonstrating the problem. Turn pde mode
> on/off in the pom and execute mvn eclipse:eclipse.
--
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] Created: (MPLUGIN-124) The generated documentation for a Mojo should show if it is a build plugin or a reporting plugin
The generated documentation for a Mojo should show if it is a build plugin or a
reporting plugin
Key: MPLUGIN-124
URL: http://jira.codehaus.org/browse/MPLUGIN-124
Project: Maven 2.x Plugin Tools
Issue Type: Improvement
Components: Plugin Plugin
Affects Versions: 2.4.2
Reporter: Dennis Lundberg
This came up on the user list:
{quote}
Isn't strange to have to define the maven-site-plugin inside just to
specify the version ?
Why maven 2 can't take into account the version declare inside ?
It seems to more natural isn't it ?
{quote}
http://www.nabble.com/Re%3A--ANN--Maven-Site-Plugin-2.0-beta-7-Released-p18311450.html
--
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] Closed: (MCHANGES-113) Allow configuration of announcement parameters from command line
[ http://jira.codehaus.org/browse/MCHANGES-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-113. Resolution: Fixed Fix Version/s: 2.1 Fixed in r674459. > Allow configuration of announcement parameters from command line > > > Key: MCHANGES-113 > URL: http://jira.codehaus.org/browse/MCHANGES-113 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Affects Versions: 2.0 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.1 > > > If you use only the announcement functions of the Changes Plugin you might > not have it configured in your POM. So you need a way to configure it from > the command line when generating the announcement after the release is done. > For example the maxEntries parameter might need to be changed if there are > lots of issues fixed. -- 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: (MPIR-109) Wrong description of in source repository overview
[
http://jira.codehaus.org/browse/MPIR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140906#action_140906
]
Vincent Siveton commented on MPIR-109:
--
I fixed French locale in r674460. I did not apply the punctuation rule since it
is an English typo rule.
> Wrong description of in source repository overview
> --
>
> Key: MPIR-109
> URL: http://jira.codehaus.org/browse/MPIR-109
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: scm
>Affects Versions: 2.0.1
>Reporter: Michael Osipov
>Assignee: Dennis Lundberg
>Priority: Minor
> Fix For: 2.1
>
>
> I have defined in my pom.xml
> {code:xml}
>
>
> scm:svn:http://svn.fckeditor.net/FCKeditor.Java/trunk
>
> scm:svn:https://svn.fckeditor.net/FCKeditor.Java/trunk
> http://dev.fckeditor.net/browser/FCKeditor.Java/trunk
>
> {code}
> MPIR writed under developer access: "Everyone can access the Subversion
> repository via HTTPS, but Committers must checkout the Subversion repository
> via HTTPS."
> As far as I understand it should say: "Everyone can access the Subversion
> repository via *HTTP*, but *committers* must checkout the Subversion
> repository via HTTPS." Unless I provide HTTPS access in anonymous access too.
> Continuing more style corrections: "For those users who are stuck behind a
> corporate firewall which is blocking http access to the Subversion
> repository," should be "For those users who are stuck behind a corporate
> firewall which is blocking *HTTP* access to the Subversion repository,"
> More: "Example : Edit the 'servers' file and add something like :" Should be:
> "*Example:* Edit the 'servers' file and add something *like:*" No space
> precedes a colon.
> Note: Bold formatting is only for highlighting purposes
--
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] Closed: (MPIR-106) Regression in 2.1-SNAPSHOT, the Project Dependencies and the Project Transitive Dependencies are the same
[ http://jira.codehaus.org/browse/MPIR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-106. Assignee: Vincent Siveton Resolution: Fixed Thanks Arnaud but the problem was in MPIR report. MPIR-76 did not update the code. I fixed it in r674456 and a snapshot was deployed. > Regression in 2.1-SNAPSHOT, the Project Dependencies and the Project > Transitive Dependencies are the same > --- > > Key: MPIR-106 > URL: http://jira.codehaus.org/browse/MPIR-106 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.1 > Environment: Windows, Maven 2.08, Project Info Reports Plugin > 2.1-SNAPSHOT >Reporter: Arnaud >Assignee: Vincent Siveton > Fix For: 2.1 > > > In the 2.0.1, in the "Project Dependencies " we find only the direct > dependency, and in the "Project Transitive Dependencies" we find all > dependency (direct and transitive). > in 2.1-SNAPSHOT, both report are same. Then, in Project Dependencies we > find the transitive dependency too. -- 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-3328) Allow multiple profile activation properties.
[ http://jira.codehaus.org/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140916#action_140916 ] Marco Sandrini commented on MNG-3328: - boolean operators could be achieved with the following syntax (let's assume with want to expression the condition ((a && b) || (c && d)) my-prop-A valueA my-prop-B valueB my-prop-C valueC my-prop-D valueD so all the conditions within one activation are considered as an AND and the different activation elements are considered as an OR. The downside of this proposal is of course that it would break the current POM model. > Allow multiple profile activation properties. > - > > Key: MNG-3328 > URL: http://jira.codehaus.org/browse/MNG-3328 > Project: Maven 2 > Issue Type: Improvement > Components: Profiles >Affects Versions: 2.0.8 >Reporter: Paul Gier > Fix For: 2.1 > > > The pom model should be changed to allow multiple properties to activate a > profile. So the profile activation section could look something like this: > > > some-value > another-value > > > This would provide more flexibility in profile activation. -- 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] Issue Comment Edited: (MNG-3328) Allow multiple profile activation properties.
[
http://jira.codehaus.org/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140916#action_140916
]
nessche edited comment on MNG-3328 at 7/7/08 7:44 AM:
-
boolean operators could be achieved with the following syntax (let's assume
with want to expression the condition ((a && b) || (c && d))
{{monospaced}
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
}
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
was (Author: nessche):
boolean operators could be achieved with the following syntax (let's assume
with want to expression the condition ((a && b) || (c && d))
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
> Allow multiple profile activation properties.
> -
>
> Key: MNG-3328
> URL: http://jira.codehaus.org/browse/MNG-3328
> Project: Maven 2
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 2.0.8
>Reporter: Paul Gier
> Fix For: 2.1
>
>
> The pom model should be changed to allow multiple properties to activate a
> profile. So the profile activation section could look something like this:
>
>
> some-value
> another-value
>
>
> This would provide more flexibility in profile activation.
--
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] Issue Comment Edited: (MNG-3328) Allow multiple profile activation properties.
[
http://jira.codehaus.org/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140916#action_140916
]
nessche edited comment on MNG-3328 at 7/7/08 7:45 AM:
-
boolean operators could be achieved with the following syntax (let's assume
with want to expression the condition ((a && b) || (c && d))
{{
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
}}
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
was (Author: nessche):
boolean operators could be achieved with the following syntax (let's assume
with want to expression the condition ((a && b) || (c && d))
{{monospaced}}
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
> Allow multiple profile activation properties.
> -
>
> Key: MNG-3328
> URL: http://jira.codehaus.org/browse/MNG-3328
> Project: Maven 2
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 2.0.8
>Reporter: Paul Gier
> Fix For: 2.1
>
>
> The pom model should be changed to allow multiple properties to activate a
> profile. So the profile activation section could look something like this:
>
>
> some-value
> another-value
>
>
> This would provide more flexibility in profile activation.
--
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] Issue Comment Edited: (MNG-3328) Allow multiple profile activation properties.
[
http://jira.codehaus.org/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140916#action_140916
]
nessche edited comment on MNG-3328 at 7/7/08 7:44 AM:
-
boolean operators could be achieved with the following syntax (let's assume
with want to expression the condition ((a && b) || (c && d))
{{monospaced}}
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
was (Author: nessche):
boolean operators could be achieved with the following syntax (let's assume
with want to expression the condition ((a && b) || (c && d))
{{monospaced}
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
}
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
> Allow multiple profile activation properties.
> -
>
> Key: MNG-3328
> URL: http://jira.codehaus.org/browse/MNG-3328
> Project: Maven 2
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 2.0.8
>Reporter: Paul Gier
> Fix For: 2.1
>
>
> The pom model should be changed to allow multiple properties to activate a
> profile. So the profile activation section could look something like this:
>
>
> some-value
> another-value
>
>
> This would provide more flexibility in profile activation.
--
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] Closed: (MEJB-26) Plugin documentation for clientExcludes property is incorrect
[ http://jira.codehaus.org/browse/MEJB-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MEJB-26. --- Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.2 Fixed in r674474. > Plugin documentation for clientExcludes property is incorrect > - > > Key: MEJB-26 > URL: http://jira.codehaus.org/browse/MEJB-26 > Project: Maven 2.x Ejb Plugin > Issue Type: Task >Affects Versions: 2.0 >Reporter: Jo Vandermeeren >Assignee: Dennis Lundberg >Priority: Trivial > Fix For: 2.2 > > > The plugin documentation for the clientExcludes property is incorrect: > > **/*Ejb.class > **/*Bean.class > > Should be > > **/*Ejb.class > **/*Bean.class > -- 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] Issue Comment Edited: (MNG-3328) Allow multiple profile activation properties.
[
http://jira.codehaus.org/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140916#action_140916
]
nessche edited comment on MNG-3328 at 7/7/08 7:46 AM:
-
boolean operators could be achieved with the following syntax (let's assume
with want to expression the condition ((a && b) || (c && d))
{code:xml}
{code}
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
{code}
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
was (Author: nessche):
boolean operators could be achieved with the following syntax (let's assume
with want to expression the condition ((a && b) || (c && d))
{{
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
}}
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
> Allow multiple profile activation properties.
> -
>
> Key: MNG-3328
> URL: http://jira.codehaus.org/browse/MNG-3328
> Project: Maven 2
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 2.0.8
>Reporter: Paul Gier
> Fix For: 2.1
>
>
> The pom model should be changed to allow multiple properties to activate a
> profile. So the profile activation section could look something like this:
>
>
> some-value
> another-value
>
>
> This would provide more flexibility in profile activation.
--
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] Issue Comment Edited: (MNG-3328) Allow multiple profile activation properties.
[
http://jira.codehaus.org/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140916#action_140916
]
nessche edited comment on MNG-3328 at 7/7/08 7:46 AM:
-
boolean operators could be achieved with the following syntax (let's assume
with want to expression the condition ((a && b) || (c && d))
{code:xml}
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
{code}
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
was (Author: nessche):
boolean operators could be achieved with the following syntax (let's assume
with want to expression the condition ((a && b) || (c && d))
{code:xml}
{code}
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
{code}
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
> Allow multiple profile activation properties.
> -
>
> Key: MNG-3328
> URL: http://jira.codehaus.org/browse/MNG-3328
> Project: Maven 2
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 2.0.8
>Reporter: Paul Gier
> Fix For: 2.1
>
>
> The pom model should be changed to allow multiple properties to activate a
> profile. So the profile activation section could look something like this:
>
>
> some-value
> another-value
>
>
> This would provide more flexibility in profile activation.
--
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] Issue Comment Edited: (MNG-3328) Allow multiple profile activation properties.
[
http://jira.codehaus.org/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140916#action_140916
]
nessche edited comment on MNG-3328 at 7/7/08 7:48 AM:
-
boolean operators could be achieved with the following syntax (let's assume
with want to express the condition ((a && b) || (c && d)) )
{code:xml}
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
{code}
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
was (Author: nessche):
boolean operators could be achieved with the following syntax (let's assume
with want to expression the condition ((a && b) || (c && d))
{code:xml}
my-prop-A
valueA
my-prop-B
valueB
my-prop-C
valueC
my-prop-D
valueD
{code}
so all the conditions within one activation are considered as an AND and the
different activation elements are considered as an OR. The downside of this
proposal is of course that it would break the current POM model.
> Allow multiple profile activation properties.
> -
>
> Key: MNG-3328
> URL: http://jira.codehaus.org/browse/MNG-3328
> Project: Maven 2
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 2.0.8
>Reporter: Paul Gier
> Fix For: 2.1
>
>
> The pom model should be changed to allow multiple properties to activate a
> profile. So the profile activation section could look something like this:
>
>
> some-value
> another-value
>
>
> This would provide more flexibility in profile activation.
--
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: (MPIR-107) Add configuration for the Project Dependency Graph / Dependency Tree
[
http://jira.codehaus.org/browse/MPIR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140918#action_140918
]
Arnaud commented on MPIR-107:
-
But these report is very light, juste show :
Used and declared dependencies
...
Used but undeclared dependencies
...
Unused but declared dependencies
...
Like we can see here :
http://maven.apache.org/plugins/maven-dependency-plugin/plugin-info.html,
the tree is not a report.
> Add configuration for the Project Dependency Graph / Dependency Tree
>
>
> Key: MPIR-107
> URL: http://jira.codehaus.org/browse/MPIR-107
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Components: dependencies
>Reporter: Arnaud
>
> Like we can configure the tree in the maven-dependency-plugin
> (http://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html),
> Why we can't configure the tree in this plugin ?
> In my project, i 'd like show only module of my compagny in the tree, and if
> there are conflict.
> so i 'd like use this configuration (it works with the commande : mvn
> dependency:tree )
> {code}
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
> ${versionDependency}
>
> net.mycompany.*
> true
>
>
>
>
> {code}
> thank you
--
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: (MAVENUPLOAD-2124) javaparser-1.0.0-bundle.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Liahushevich updated MAVENUPLOAD-2124: --- Attachment: javaparser-1.0.0-bundle.jar updated javaparser-1.0.0-bundle.jar with pom.xml modified > javaparser-1.0.0-bundle.jar > --- > > Key: MAVENUPLOAD-2124 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2124 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Alexandr Liahushevich > Attachments: javaparser-1.0.0-bundle.jar, javaparser-1.0.0-bundle.jar > > > From: Julio Gesser [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2008 2:38 PM > To: Alexandr Liahushevich > Subject: Re: Java 1.5 Parser - request to put sources into the maven > repository > > Helo Alexandr, > yes, you can put this distribution there, but I think you need to put the > license too. > best regards, > Júlio Vilmar Gesser > 2008/6/24 Alexandr Liahushevich <[EMAIL PROTECTED]>: > One more question please. > We are using Maven technology for our projects. > Is it ok for you and your team that we want to put your > javaparser_2008-06-19.jar file in the http://repo1.maven.org/maven2/ central > maven repository? -- 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: (MAVENUPLOAD-2124) javaparser-1.0.0-bundle.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140921#action_140921 ] Alexandr Liahushevich commented on MAVENUPLOAD-2124: 07/Jul/08: use last attached javaparser-1.0.0-bundle.jar file(2) > javaparser-1.0.0-bundle.jar > --- > > Key: MAVENUPLOAD-2124 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2124 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Alexandr Liahushevich > Attachments: javaparser-1.0.0-bundle.jar, javaparser-1.0.0-bundle.jar > > > From: Julio Gesser [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2008 2:38 PM > To: Alexandr Liahushevich > Subject: Re: Java 1.5 Parser - request to put sources into the maven > repository > > Helo Alexandr, > yes, you can put this distribution there, but I think you need to put the > license too. > best regards, > Júlio Vilmar Gesser > 2008/6/24 Alexandr Liahushevich <[EMAIL PROTECTED]>: > One more question please. > We are using Maven technology for our projects. > Is it ok for you and your team that we want to put your > javaparser_2008-06-19.jar file in the http://repo1.maven.org/maven2/ central > maven repository? -- 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: (MEJB-28) outputDirectory is not created before packaging
[
http://jira.codehaus.org/browse/MEJB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140922#action_140922
]
Dennis Lundberg commented on MEJB-28:
-
Can you give us a complete pom.xml that we can use to test this?
> outputDirectory is not created before packaging
> ---
>
> Key: MEJB-28
> URL: http://jira.codehaus.org/browse/MEJB-28
> Project: Maven 2.x Ejb Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Ron Piterman
>Priority: Minor
>
> When using the jar plugin, outputDirectory is being cerated prior to creating
> the jar.
> The ejb plugin however fails if specifying an outputDirectory which does not
> exist -
> So, specifying something like ${project.build.directory}/jar will always fail
> after a clean.
--
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: (MEJB-27) duplicated ejb-jar.xml
[ http://jira.codehaus.org/browse/MEJB-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140923#action_140923 ] Dennis Lundberg commented on MEJB-27: - You are getting one copy in /meta-inf/ from the Resource Plugin because you are specifying the element. You get the other copy in /META-INF/ from the EJB Plugin. Note the difference in case of the directory name. > duplicated ejb-jar.xml > -- > > Key: MEJB-27 > URL: http://jira.codehaus.org/browse/MEJB-27 > Project: Maven 2.x Ejb Plugin > Issue Type: Bug >Affects Versions: 2.0, 2.1 > Environment: Windows XP, jdk 1.4.2, maven 2.0.7 >Reporter: Stefan Chis > Attachments: trainingwall_mdb-1.0.0.jar > > > The ejb-jar.xml descriptor is duplicated in the generated jar file (the ejb > archive). The project is a J2EE multi-module project. The weird thing, is > this project is the only one affected, other J2EE multi-module project are > built just fine. > Anyway, I am attaching the generated artifact, as evidence of the problem. > Also, here is the relevant snippet from the child pom: > > > src/main/resources/meta-inf > meta-inf > > > > > org.apache.maven.plugins > maven-ejb-plugin > > > >true > > > > > > Problem affects the versions 2.0, 2.1of the ejb plugin. -- 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: (MEJB-24) It should be possible not to include the META-INF/maven directory in produced jars
[
http://jira.codehaus.org/browse/MEJB-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140924#action_140924
]
Dennis Lundberg commented on MEJB-24:
-
This works for me with version 2.1 of the plugin.
I use this plugin configuration:
{noformat}
false
{noformat}
> It should be possible not to include the META-INF/maven directory in produced
> jars
> --
>
> Key: MEJB-24
> URL: http://jira.codehaus.org/browse/MEJB-24
> Project: Maven 2.x Ejb Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Prasad Kashyap
>
> http://jira.codehaus.org/browse/MNG-1598
> The in the other archiver plugins exclude the pom and
> .properties files from the created archives. If the packaging of a pom is set
> to "ejb", then the produced jar still contains these maven descriptors.
> My 2.1 maven-jar-plugin is configured to
> false. When my pom packaging is set
> to "jar", the descriptors does get excluded.
> Problem is with the "ejb" packaging and/or maven-ejb-plugin.
--
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] Closed: (MEJB-25) Classifiers do not work during deploy phase
[ http://jira.codehaus.org/browse/MEJB-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MEJB-25. --- Resolution: Won't Fix See issue in the deploy plugin. > Classifiers do not work during deploy phase > --- > > Key: MEJB-25 > URL: http://jira.codehaus.org/browse/MEJB-25 > Project: Maven 2.x Ejb Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Tim Meighen > Attachments: classifier-test.tar.gz > > > Classifiers work fine during a mvn install, but during mvn deploy the build > fails. I believe that this is due to the artifact being added as an > attachment without building the "non-classifier" version (i.e. there is no > artifact defined). > I've attached a sample project to demonstrate. You will need to fill in the > URL to your snapshot repo -- 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] Closed: (MSHARED-16) stage dies at normalization of relative path
[ http://jira.codehaus.org/browse/MSHARED-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSHARED-16. -- Resolution: Fixed Fix Version/s: maven-doxia-tools 1.0 > stage dies at normalization of relative path > > > Key: MSHARED-16 > URL: http://jira.codehaus.org/browse/MSHARED-16 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-doxia-tools > Environment: Linux >Reporter: Martin von Gagern > Fix For: maven-doxia-tools 1.0 > > Attachments: normalizeRelativePaths.patch, testcase.zip > > > Since r640091, DefaultSiteTool from maven-doxia-tools tries to normalize > paths, which fails, as the current plexus-utils don't handle normalization of > relative paths, and the stage mojo seems to use them quite extensively. > I have attached a small testcase, a parent project with a single child, and > site:stage as the default goal, so you can simply run "mvn" on the parent. > Debugging this shows that FileUtils.normalize is handed a path starting in > "../../". > I have also attached a patch to plexus-utils that makes FileUtils.normalize > handle relative paths, but I'm not sure if this would be intended, and I > can't test it, because I can't get maven use the latest snapshot of > plexus-utils, even if stated as an explicit dependency of the site plugin. > See also: > http://svn.apache.org/viewvc/maven/shared/trunk/maven-doxia-tools/src/main/java/org/apache/maven/doxia/tools/DefaultSiteTool.java?r1=637431&r2=640091&diff_format=h#l72 > http://fisheye.codehaus.org/browse/plexus/plexus-utils/trunk/src/main/java/org/codehaus/plexus/util/FileUtils.java -- 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] Closed: (MEJB-24) It should be possible not to include the META-INF/maven directory in produced jars
[ http://jira.codehaus.org/browse/MEJB-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MEJB-24. --- Resolution: Fixed Fix Version/s: 2.1 > It should be possible not to include the META-INF/maven directory in produced > jars > -- > > Key: MEJB-24 > URL: http://jira.codehaus.org/browse/MEJB-24 > Project: Maven 2.x Ejb Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Prasad Kashyap > Fix For: 2.1 > > > http://jira.codehaus.org/browse/MNG-1598 > The in the other archiver plugins exclude the pom and > .properties files from the created archives. If the packaging of a pom is set > to "ejb", then the produced jar still contains these maven descriptors. > My 2.1 maven-jar-plugin is configured to > false. When my pom packaging is set > to "jar", the descriptors does get excluded. > Problem is with the "ejb" packaging and/or maven-ejb-plugin. -- 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] Created: (MDEPLOY-82) Enable resolution of dependency version ranges
Enable resolution of dependency version ranges -- Key: MDEPLOY-82 URL: http://jira.codehaus.org/browse/MDEPLOY-82 Project: Maven 2.x Deploy Plugin Issue Type: New Feature Reporter: Paul Gier It would be helpful when deploying to be have the option to change the dependency version ranges to the specific version used during that build. This would allow a version range in the local pom, but the deployed pom in the repository (and in the tag when releasing) would collapse the range into the version that was used during the build. -- 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-1977) Global dependency exclusions
[ http://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140936#action_140936 ] Clive Jevons commented on MNG-1977: --- I'm currently also suffering from the lack of this feature and would be extremely grateful to see this one added :) Cheers, C > Global dependency exclusions > > > Key: MNG-1977 > URL: http://jira.codehaus.org/browse/MNG-1977 > Project: Maven 2 > Issue Type: New Feature > Components: POM >Reporter: Kees de Kooter > Fix For: 2.1 > > > I depend on some libraries, which in turn depend on something > (which in turn depend on something) that I don't want, because I declare > some other artifact in my pom.xml. > A concrete example: I don't want that the artifact "xerces" is imported in > my project because I declare to depend on "xercesImpl" which ships newer > libraries but with the same namespaces. > I guess I would need an "exclude transitive dependency at all", either > globally or from this and that artifact. I saw the tag, but it > forces me to be very verbose and have exact control on what is required by a > dependency. -- 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: (MDEPLOY-82) Enable resolution of dependency version ranges
[ http://jira.codehaus.org/browse/MDEPLOY-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated MDEPLOY-82: - Description: It would be helpful when deploying to be have the option to change the dependency version ranges to the specific version used during that build. This would allow the local pom to contain a version range for one or more dependencies, but the deployed pom in the repository (and in the tag when releasing) would collapse the range into the version that was used during the build. (was: It would be helpful when deploying to be have the option to change the dependency version ranges to the specific version used during that build. This would allow a version range in the local pom, but the deployed pom in the repository (and in the tag when releasing) would collapse the range into the version that was used during the build.) > Enable resolution of dependency version ranges > -- > > Key: MDEPLOY-82 > URL: http://jira.codehaus.org/browse/MDEPLOY-82 > Project: Maven 2.x Deploy Plugin > Issue Type: New Feature >Reporter: Paul Gier > > It would be helpful when deploying to be have the option to change the > dependency version ranges to the specific version used during that build. > This would allow the local pom to contain a version range for one or more > dependencies, but the deployed pom in the repository (and in the tag when > releasing) would collapse the range into the version that was used during the > build. -- 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] Created: (MAVENUPLOAD-2139) JGoodies Forms 1.1-preview bundle
JGoodies Forms 1.1-preview bundle - Key: MAVENUPLOAD-2139 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2139 Project: Maven Upload Requests Issue Type: Wish Reporter: Tim Kettler Attachments: jgoodies-forms-1.1-preview-bundle.jar An earlier version of JGoodies Forms is already present in central: http://repo1.maven.org/maven2/com/jgoodies/forms/ Licence is BSD, as shown on the linked project URL. -- 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] Created: (MAVENUPLOAD-2140) IntelliJ IDEA 7.0.3 Redistributable Jars
IntelliJ IDEA 7.0.3 Redistributable Jars Key: MAVENUPLOAD-2140 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2140 Project: Maven Upload Requests Issue Type: Wish Reporter: Tim Kettler Earlier versions are already present in central: http://www.ibiblio.org/maven2/com/intellij/ Licensing is ASL 2.0 Bundle URLS: http://criticalsection.org/bundles/annotations-7.0.3-bundle.jar http://criticalsection.org/bundles/extensions-7.0.3-bundle.jar http://criticalsection.org/bundles/forms_rt-7.0.3-bundle.jar http://criticalsection.org/bundles/javac2-7.0.3-bundle.jar http://criticalsection.org/bundles/javaee-openapi-7.0.3-bundle.jar http://criticalsection.org/bundles/openapi-7.0.3-bundle.jar -- 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: (MAVENUPLOAD-2140) IntelliJ IDEA 7.0.3 Redistributable Jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kettler updated MAVENUPLOAD-2140: - Attachment: extensions-7.0.3-bundle.jar > IntelliJ IDEA 7.0.3 Redistributable Jars > > > Key: MAVENUPLOAD-2140 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2140 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Tim Kettler > Attachments: annotations-7.0.3-bundle.jar, > extensions-7.0.3-bundle.jar, forms_rt-7.0.3-bundle.jar, > javac2-7.0.3-bundle.jar, javaee-openapi-7.0.3-bundle.jar > > > Earlier versions are already present in central: > http://www.ibiblio.org/maven2/com/intellij/ > Licensing is ASL 2.0 > Bundle URLS: > http://criticalsection.org/bundles/annotations-7.0.3-bundle.jar > http://criticalsection.org/bundles/extensions-7.0.3-bundle.jar > http://criticalsection.org/bundles/forms_rt-7.0.3-bundle.jar > http://criticalsection.org/bundles/javac2-7.0.3-bundle.jar > http://criticalsection.org/bundles/javaee-openapi-7.0.3-bundle.jar > http://criticalsection.org/bundles/openapi-7.0.3-bundle.jar -- 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: (MAVENUPLOAD-2140) IntelliJ IDEA 7.0.3 Redistributable Jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kettler updated MAVENUPLOAD-2140: - Attachment: javaee-openapi-7.0.3-bundle.jar > IntelliJ IDEA 7.0.3 Redistributable Jars > > > Key: MAVENUPLOAD-2140 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2140 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Tim Kettler > Attachments: annotations-7.0.3-bundle.jar, > extensions-7.0.3-bundle.jar, forms_rt-7.0.3-bundle.jar, > javac2-7.0.3-bundle.jar, javaee-openapi-7.0.3-bundle.jar > > > Earlier versions are already present in central: > http://www.ibiblio.org/maven2/com/intellij/ > Licensing is ASL 2.0 > Bundle URLS: > http://criticalsection.org/bundles/annotations-7.0.3-bundle.jar > http://criticalsection.org/bundles/extensions-7.0.3-bundle.jar > http://criticalsection.org/bundles/forms_rt-7.0.3-bundle.jar > http://criticalsection.org/bundles/javac2-7.0.3-bundle.jar > http://criticalsection.org/bundles/javaee-openapi-7.0.3-bundle.jar > http://criticalsection.org/bundles/openapi-7.0.3-bundle.jar -- 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: (MAVENUPLOAD-2140) IntelliJ IDEA 7.0.3 Redistributable Jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kettler updated MAVENUPLOAD-2140: - Attachment: annotations-7.0.3-bundle.jar > IntelliJ IDEA 7.0.3 Redistributable Jars > > > Key: MAVENUPLOAD-2140 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2140 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Tim Kettler > Attachments: annotations-7.0.3-bundle.jar, > extensions-7.0.3-bundle.jar, forms_rt-7.0.3-bundle.jar, > javac2-7.0.3-bundle.jar, javaee-openapi-7.0.3-bundle.jar > > > Earlier versions are already present in central: > http://www.ibiblio.org/maven2/com/intellij/ > Licensing is ASL 2.0 > Bundle URLS: > http://criticalsection.org/bundles/annotations-7.0.3-bundle.jar > http://criticalsection.org/bundles/extensions-7.0.3-bundle.jar > http://criticalsection.org/bundles/forms_rt-7.0.3-bundle.jar > http://criticalsection.org/bundles/javac2-7.0.3-bundle.jar > http://criticalsection.org/bundles/javaee-openapi-7.0.3-bundle.jar > http://criticalsection.org/bundles/openapi-7.0.3-bundle.jar -- 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: (MAVENUPLOAD-2140) IntelliJ IDEA 7.0.3 Redistributable Jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kettler updated MAVENUPLOAD-2140: - Attachment: javac2-7.0.3-bundle.jar > IntelliJ IDEA 7.0.3 Redistributable Jars > > > Key: MAVENUPLOAD-2140 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2140 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Tim Kettler > Attachments: annotations-7.0.3-bundle.jar, > extensions-7.0.3-bundle.jar, forms_rt-7.0.3-bundle.jar, > javac2-7.0.3-bundle.jar, javaee-openapi-7.0.3-bundle.jar > > > Earlier versions are already present in central: > http://www.ibiblio.org/maven2/com/intellij/ > Licensing is ASL 2.0 > Bundle URLS: > http://criticalsection.org/bundles/annotations-7.0.3-bundle.jar > http://criticalsection.org/bundles/extensions-7.0.3-bundle.jar > http://criticalsection.org/bundles/forms_rt-7.0.3-bundle.jar > http://criticalsection.org/bundles/javac2-7.0.3-bundle.jar > http://criticalsection.org/bundles/javaee-openapi-7.0.3-bundle.jar > http://criticalsection.org/bundles/openapi-7.0.3-bundle.jar -- 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: (MAVENUPLOAD-2140) IntelliJ IDEA 7.0.3 Redistributable Jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kettler updated MAVENUPLOAD-2140: - Attachment: forms_rt-7.0.3-bundle.jar > IntelliJ IDEA 7.0.3 Redistributable Jars > > > Key: MAVENUPLOAD-2140 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2140 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Tim Kettler > Attachments: annotations-7.0.3-bundle.jar, > extensions-7.0.3-bundle.jar, forms_rt-7.0.3-bundle.jar, > javac2-7.0.3-bundle.jar, javaee-openapi-7.0.3-bundle.jar > > > Earlier versions are already present in central: > http://www.ibiblio.org/maven2/com/intellij/ > Licensing is ASL 2.0 > Bundle URLS: > http://criticalsection.org/bundles/annotations-7.0.3-bundle.jar > http://criticalsection.org/bundles/extensions-7.0.3-bundle.jar > http://criticalsection.org/bundles/forms_rt-7.0.3-bundle.jar > http://criticalsection.org/bundles/javac2-7.0.3-bundle.jar > http://criticalsection.org/bundles/javaee-openapi-7.0.3-bundle.jar > http://criticalsection.org/bundles/openapi-7.0.3-bundle.jar -- 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: (MAVENUPLOAD-2140) IntelliJ IDEA 7.0.3 Redistributable Jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kettler updated MAVENUPLOAD-2140: - Attachment: openapi-7.0.3-bundle.jar > IntelliJ IDEA 7.0.3 Redistributable Jars > > > Key: MAVENUPLOAD-2140 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2140 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Tim Kettler > Attachments: annotations-7.0.3-bundle.jar, > extensions-7.0.3-bundle.jar, forms_rt-7.0.3-bundle.jar, > javac2-7.0.3-bundle.jar, javaee-openapi-7.0.3-bundle.jar, > openapi-7.0.3-bundle.jar > > > Earlier versions are already present in central: > http://www.ibiblio.org/maven2/com/intellij/ > Licensing is ASL 2.0 > Bundle URLS: > http://criticalsection.org/bundles/annotations-7.0.3-bundle.jar > http://criticalsection.org/bundles/extensions-7.0.3-bundle.jar > http://criticalsection.org/bundles/forms_rt-7.0.3-bundle.jar > http://criticalsection.org/bundles/javac2-7.0.3-bundle.jar > http://criticalsection.org/bundles/javaee-openapi-7.0.3-bundle.jar > http://criticalsection.org/bundles/openapi-7.0.3-bundle.jar -- 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] Created: (MNG-3658) improve maven embedder documentation
improve maven embedder documentation Key: MNG-3658 URL: http://jira.codehaus.org/browse/MNG-3658 Project: Maven 2 Issue Type: Wish Components: Embedding Affects Versions: 2.0.7 Reporter: Benjamin Pochat Hi, I would like to use the maven embedder. What is described in the maven website seems wonderfull (http://maven.apache.org/guides/mini/guide-embedding-m2.html) But when I tried to go further, I was not able to find a precise documentation about the API that seems to be provided. The documentation that comes out from Google (http://repo1.maven.org/maven2/org/apache/maven/maven-embedder/2.0.4/) looks like out of date : maven website describes that the class MavenEmbedder implements a method "execute" returning a MavenExecutionResult ; but this method is not documented in the javadoc coming out from Google. It even looks like the maven embedder is not included in the standard distribution of maven : there is no classe named MavenEmbedder in the lib maven-core-2.0.X.jar, neither in the dependecies of the pom maven-core-2.0.X.pom. In other words, I have nothing to make maven embedding work. Regards, Benjamin -- 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] Closed: (MARTIFACT-27) [regression] unable to build ServiceMix 3 - incompatibility in Artifact API
[ http://jira.codehaus.org/browse/MARTIFACT-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MARTIFACT-27. - Assignee: Brett Porter Resolution: Fixed fixed, and also double checked clirr > [regression] unable to build ServiceMix 3 - incompatibility in Artifact API > --- > > Key: MARTIFACT-27 > URL: http://jira.codehaus.org/browse/MARTIFACT-27 > Project: Maven Artifact > Issue Type: Bug >Affects Versions: 3.0-alpha-1 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 3.0-alpha-1 > > > building: > https://svn.apache.org/repos/asf/servicemix/smx3/trunk/deployables/serviceengines/servicemix-lwcontainer > results: > Exception in thread "main" java.lang.NoSuchMethodError: > org.apache.maven.artifact.resolver.ArtifactResolutionResult.setArtifactResolutionNodes(Ljava/util/Set;)V > at > org.apache.servicemix.maven.plugin.jbi.GraphArtifactCollector.collect(GraphArtifactCollector.java:92) > at > org.apache.servicemix.maven.plugin.jbi.AbstractJbiMojo.resolveProject(AbstractJbiMojo.java:214) > at > org.apache.servicemix.maven.plugin.jbi.GenerateComponentDescriptorMojo.generateJbiDescriptor(GenerateComponentDescriptorMojo.java:217) > at > org.apache.servicemix.maven.plugin.jbi.GenerateComponentDescriptorMojo.execute(GenerateComponentDescriptorMojo.java:158) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:638) -- 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: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects
[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140964#action_140964 ] Sébastien Moreno commented on MRELEASE-261: --- Yes it's work fine, and it's not a bad concept to have a "build" pom and a "parent" separated. In our case, the "root" pom is a child of the "parent" in order to benefit the release change version system and retrieving SCM information. The only bad news is that the generated site mention the "root" module as a real separated module. But it could be used as a kind of information build summary page. > release:prepare shouls support flat directory multimodule projects > -- > > Key: MRELEASE-261 > URL: http://jira.codehaus.org/browse/MRELEASE-261 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Environment: linux / maven2 / svn >Reporter: [EMAIL PROTECTED] > Attachments: PrepareReleaseMojo.patch > > > What I mean by flat file structure firstly. > parent/pom.xml > module1/pom.xml > module2/pom.xml > . > . > . > module15/pom.xml > the parent references the modules like so > > ../module1 > ../module2 > . > . > . > ../module15 > > When i release:prepare only the parent project is tagged the modules > projects versions are incremented etc but the modules are not tagged in svn. > I use this structure as i use eclipse as my IDE. > I would love to see a fix for the issue marked as closed here > http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand > each submodule of the projects but it would be so nice to have the release > plugin do this for me. > forgive my english. -- 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: (MASSEMBLY-190) Problem with dependency conflict resolution on multi-module project
[ http://jira.codehaus.org/browse/MASSEMBLY-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140972#action_140972 ] Clive Jevons commented on MASSEMBLY-190: Has there been any progress on this? Is there a known workaround? I've currently got this problem in 2.0.9 with a WAR assembly. My WAR includes the ejb-client. But by doing so, I transitively include all the dependencies the ejb (not the client) needs. So I 'exclusion' them from the WAR. If I build just the WAR, this works find. If I build the WAR as part of the aggregate build, then the exclusions are ignored and I end up having all of the dependencies I'd excluded in WEB-INF/lib Cheers, C > Problem with dependency conflict resolution on multi-module project > --- > > Key: MASSEMBLY-190 > URL: http://jira.codehaus.org/browse/MASSEMBLY-190 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: Using maven 2.0.5 and assembly 2.2-SNAPSHOT >Reporter: Frédéric ESNAULT > Fix For: 2.2-beta-3 > > > Hi, > I'm trying to use the assembly plugin to gather all the jars of my project, > including all dependencies. > As the project is composed of several modules, I use a descriptor which looks > like this : > > bin > > zip > > false > > > > / > false > true > > > > > It seems to work fine at first sight - it creates a zip containing all the > jar files. However, I find in the archive several instances of the same > dependency with differents versions, for instance asm-1.5.3 and asm-2.2.3. > This is a surprise as maven is supposed to take care of conflict resolution. > When I look at a detailed trace, it appears that conflict resolution is done > but on each module independently. But my modules are intended to work > together and I expect to get an assembly with only one version of each > dependency found on the whole set of mudules. It seems to me that conflict > resolution is not managed properly in this use case. -- 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] Closed: (MAVENUPLOAD-2138) org.aspectj:aspectjtools:1.6.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2138. --- Assignee: Carlos Sanchez Resolution: Fixed > org.aspectj:aspectjtools:1.6.1 > -- > > Key: MAVENUPLOAD-2138 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2138 > Project: Maven Upload Requests > Issue Type: Improvement >Reporter: David J. M. Karlsen >Assignee: Carlos Sanchez > -- 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] Closed: (MAVENUPLOAD-2137) org.aspectj:aspectjrt:1.6.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2137. --- Assignee: Carlos Sanchez Resolution: Fixed > org.aspectj:aspectjrt:1.6.1 > --- > > Key: MAVENUPLOAD-2137 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2137 > Project: Maven Upload Requests > Issue Type: Improvement >Reporter: David J. M. Karlsen >Assignee: Carlos Sanchez > -- 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] Closed: (MAVENUPLOAD-2136) org.aspectj:aspectjlib:1.6.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2136. --- Assignee: Carlos Sanchez Resolution: Fixed > org.aspectj:aspectjlib:1.6.1 > > > Key: MAVENUPLOAD-2136 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2136 > Project: Maven Upload Requests > Issue Type: Improvement >Reporter: David J. M. Karlsen >Assignee: Carlos Sanchez > -- 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] Closed: (MAVENUPLOAD-2135) org.aspectj:aspectjweaver:1.6.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2135. --- Assignee: Carlos Sanchez Resolution: Fixed next tiem please put all bundle urls in one issue > org.aspectj:aspectjweaver:1.6.1 > --- > > Key: MAVENUPLOAD-2135 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2135 > Project: Maven Upload Requests > Issue Type: Improvement >Reporter: David J. M. Karlsen >Assignee: Carlos Sanchez > -- 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] Closed: (MPIR-110) Update code due to deprecated classes in maven-dependency-tree:1.1
[ http://jira.codehaus.org/browse/MPIR-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-110. Assignee: Vincent Siveton Resolution: Fixed Fixed in r674664, snapshot deployed. > Update code due to deprecated classes in maven-dependency-tree:1.1 > -- > > Key: MPIR-110 > URL: http://jira.codehaus.org/browse/MPIR-110 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependencies >Affects Versions: 2.1 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.1 > > > MPIR-76 updated the maven-dependency-tree to 1.1 > DependencyTree is now deprecated. -- 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: (MPIR-111) Make Classifier and Optional column in dependies report "optional" in the renderer
[ http://jira.codehaus.org/browse/MPIR-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MPIR-111: - Affects Version/s: 2.1 Fix Version/s: 2.1 > Make Classifier and Optional column in dependies report "optional" in the > renderer > -- > > Key: MPIR-111 > URL: http://jira.codehaus.org/browse/MPIR-111 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Vincent Siveton > Fix For: 2.1 > > > Actually, Classifier and Optional columns are always presents. It should be > better to add them only if they have different values. -- 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] Created: (MPIR-111) Make Classifier and Optional column in dependies report "optional" in the renderer
Make Classifier and Optional column in dependies report "optional" in the renderer -- Key: MPIR-111 URL: http://jira.codehaus.org/browse/MPIR-111 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Reporter: Vincent Siveton Fix For: 2.1 Actually, Classifier and Optional columns are always presents. It should be better to add them only if they have different values. -- 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: (MSOURCES-32) Usage dependency-plugin with source-plugin causes BUILD ERROR
[ http://jira.codehaus.org/browse/MSOURCES-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140991#action_140991 ] rob g commented on MSOURCES-32: --- I ran into this same problem when working with the cobertura plugin as well and I believe I've traced the problem back to the DefaultLifecycleExecutor and the DefaultPluginManager. The error appears to be triggered when executing a mojo which forks the project lifecycle (which is true for both the maven-source-plugin and the cobertura-maven-plugin) *and* another build plugin has been configured to _not_ be inherited (as is the case with the dependency:copy mojo in the attached sample project). The role of the "inherited" attribute in triggering the error can be seen by commenting out the declaration in the sample pom, which will enable the build to pass. What I think is happening is that when MojoExecutions are created by the DefaultLifecycleExecutor, the execution configuration is not populated. In addition, when the MavenProject is cloned to be the "executionProject" for the forked lifecycle, only those plugins which have inherited == true are copied over to the clone by ModelUtils.mergePluginLists(). Thus by the time that the DefaultPluginManager is confirming that the mojo is properly configured, you have an execution object which was constructed from the original project without any configuration elements and it is being evaluated in the scope of a cloned project which doesn't include the plugin definition. > Usage dependency-plugin with source-plugin causes BUILD ERROR > - > > Key: MSOURCES-32 > URL: http://jira.codehaus.org/browse/MSOURCES-32 > Project: Maven 2.x Source Plugin > Issue Type: Bug > Environment: Maven version: 2.0.8, Java version: 1.5.0_12, OS name: > "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Valeriy Gavrilovets > Attachments: log.txt, MSOURCES-32.zip > > > I use dependecy-plugin to copy some jars into the project. I attach it to > initialize phase. If i do so, the source-plugin gets silly. > [INFO] [jar:jar] > [INFO] Building jar: > c:\share\sample-project\ISSUE\target\ISSUE-0.0.1-SNAPSHOT.jar > [INFO] Preparing source:jar > [WARNING] Removing: jar from forked lifecycle, to prevent recursive > invocation. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] One or more required plugin parameters are invalid/missing for > 'dependency:copy' > [0] Inside the definition for plugin 'maven-dependency-plugin' specify the > following: > > ... > VALUE > . > I get silly too. =( -- 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: (MSOURCES-32) Usage dependency-plugin with source-plugin causes BUILD ERROR
[ http://jira.codehaus.org/browse/MSOURCES-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Golkosky updated MSOURCES-32: Attachment: maven.out Attaching maven -X output which contains the stacktrace. > Usage dependency-plugin with source-plugin causes BUILD ERROR > - > > Key: MSOURCES-32 > URL: http://jira.codehaus.org/browse/MSOURCES-32 > Project: Maven 2.x Source Plugin > Issue Type: Bug > Environment: Maven version: 2.0.8, Java version: 1.5.0_12, OS name: > "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Valeriy Gavrilovets > Attachments: log.txt, maven.out, MSOURCES-32.zip > > > I use dependecy-plugin to copy some jars into the project. I attach it to > initialize phase. If i do so, the source-plugin gets silly. > [INFO] [jar:jar] > [INFO] Building jar: > c:\share\sample-project\ISSUE\target\ISSUE-0.0.1-SNAPSHOT.jar > [INFO] Preparing source:jar > [WARNING] Removing: jar from forked lifecycle, to prevent recursive > invocation. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] One or more required plugin parameters are invalid/missing for > 'dependency:copy' > [0] Inside the definition for plugin 'maven-dependency-plugin' specify the > following: > > ... > VALUE > . > I get silly too. =( -- 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] Created: (MNG-3659) Securing Artifacts
Securing Artifacts -- Key: MNG-3659 URL: http://jira.codehaus.org/browse/MNG-3659 Project: Maven 2 Issue Type: New Feature Reporter: Davanum Srinivas Email from Roy on [EMAIL PROTECTED]: == Yes, it would be nice if Maven was more secure, properly checked signatures, and properly delegated namespaces so that third-parties would be unable to add artifacts within other org's trees. None of those issues are specific to incubator. == Please see here for full context : http://markmail.org/message/dpv2vbtw6ygeze4z -- 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-2477) Implement repository security improvements for verification of downloaded artifacts
[ http://jira.codehaus.org/browse/MNG-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140994#action_140994 ] Brett Porter commented on MNG-2477: --- the page was moved to http://docs.codehaus.org/display/MAVEN/Repository+Security > Implement repository security improvements for verification of downloaded > artifacts > --- > > Key: MNG-2477 > URL: http://jira.codehaus.org/browse/MNG-2477 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Reporter: Brett Porter > Fix For: 2.1 > > > http://docs.codehaus.org/display/MAVEN/Repository+Security+Improvements -- 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] Closed: (MNG-3659) Securing Artifacts
[ http://jira.codehaus.org/browse/MNG-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-3659. - Resolution: Duplicate please comment on this proposal: http://docs.codehaus.org/display/MAVEN/Repository+Security > Securing Artifacts > -- > > Key: MNG-3659 > URL: http://jira.codehaus.org/browse/MNG-3659 > Project: Maven 2 > Issue Type: New Feature >Reporter: Davanum Srinivas > > Email from Roy on [EMAIL PROTECTED]: > == > Yes, it would be nice if Maven was more secure, properly checked > signatures, and properly delegated namespaces so that third-parties > would be unable to add artifacts within other org's trees. None of > those issues are specific to incubator. > == > Please see here for full context : > http://markmail.org/message/dpv2vbtw6ygeze4z -- 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
