[jira] Commented: (MJAR-138) jar:test-jar is skipped when maven.test.skip=true
[
http://jira.codehaus.org/browse/MJAR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234204#action_234204
]
Benjamin Bentmann commented on MJAR-138:
{{maven.test.skip=true}} suppresses multiple things: test compilation, test
execution and test jar packaging. The later was intentionally done as per
MJAR-90.
Independently how this should be addressed in the future, for now a simple
workaround is to use {{skipTests=true}} instead. This suppresses test execution
only, but produces a proper test-jar which allows other modules to both
properly resolve their dependencies and even compile against those.
> jar:test-jar is skipped when maven.test.skip=true
> -
>
> Key: MJAR-138
> URL: http://jira.codehaus.org/browse/MJAR-138
> Project: Maven 2.x Jar Plugin
> Issue Type: Improvement
>Affects Versions: 2.3.1
> Environment: jar:test-jar
>Reporter: Andrew Hughes
>
> Not sure if this is a bug or improvement...
> Example:
> * ./pom.xml
> * ./moduleA/pom.xml
> * ./moduleB/pom.xml
> Situation:
> * moduleA produces moduleA-1.2.3-test.jar with the jar:test-jar goal
> * moduleB consumes moduleA-1.2.3-test.jar as a
> ...test
> Problem:
> * When -Dmaven.test.skip=true the moduleA-1.2.3-test.jar is never built.
> * Then when moduleB tries to build, it's moduleA-1.2.3-test.jar dependency is
> unresolved. FAIL! Even with -Dmaven.test.skip=true this will fail.
> You might argue that this is a bug with dependency resolution with
> -Dmaven.test.skip=true - should a missing dependency @ test scope really fail
> the build??? It probably should - which is why the bug is submitted here :)
> I've no idea what could be done to fix this either?
> ---
> p.s. for anyone with this bug the only workaround I can suggest is running
> another module...
> ./moduleA-test/pom.xml
> and have
> ...moduleA-test...test
--
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: (MCOMPILER-109) JavacCompiler treat localized warning messages as errors
[
http://jira.codehaus.org/browse/MCOMPILER-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MCOMPILER-109:
Affects Version/s: 2.3.1
Fix Version/s: (was: 2.4)
2.3.2
> JavacCompiler treat localized warning messages as errors
>
>
> Key: MCOMPILER-109
> URL: http://jira.codehaus.org/browse/MCOMPILER-109
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 2.3.1
>Reporter: Kohsuke Kawaguchi
>Assignee: Benjamin Bentmann
> Fix For: 2.3.2
>
>
> This is really a bug in plexus-compiler-javac, not that of a Maven plugin.
> Javac uses localized messages for "error" and "warning" for languages like
> Japanese, but JavacCompiler.parseModernStream(...) and parseModernError(...)
> is hard-coded to only understand English words "warning" and "error".
> In particular, in line 535, the code treats any keyword but "warning" as
> errors, so the Japanese word "警告" (meaning warning) is
> interpreted as an error.
> {code}
> isError = !msg.startsWith( WARNING_PREFIX );
> {code}
> As a fix, I suggest you check the exit code from javac to determine if there
> were any errors --- if it returns 0, treat everything as warnings.
--
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: (MCOMPILER-106) -Xlint -Xlint:-path argument quoting problem
[ http://jira.codehaus.org/browse/MCOMPILER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MCOMPILER-106. --- Resolution: Duplicate Assignee: Benjamin Bentmann > -Xlint -Xlint:-path argument quoting > problem > - > > Key: MCOMPILER-106 > URL: http://jira.codehaus.org/browse/MCOMPILER-106 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: java version "1.5.0_20" >Reporter: deckrider >Assignee: Benjamin Bentmann > > -Xlint -Xlint:-path gives the following > error: > javac: invalid flag: -Xlint -Xlint:-path > The workaround/hack illustrates the quoting problem: > -Xlint" "-Xlint:-path > And now to quote the docs at > http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#compilerArgument > Sets the unformatted argument string to be passed to the compiler if fork is > set to true. This is because the list of valid arguments passed to a Java > compiler varies based on the compiler version. -- 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: (MNGSITE-102) Misleading documentation on the schema of profiles.xml
[
http://jira.codehaus.org/browse/MNGSITE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNGSITE-102:
--
Description:
The documentation at
http://maven.apache.org/guides/introduction/introduction-to-profiles.html seems
to indicate that the schema for profiles.xml is
{code:xml}
...
{code}
However, it seems that now a root element of ... is
required. A sample working profiles.xml file looks like:
{code:xml}http://maven.apache.org/PROFILES/1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/PROFILES/1.0.0
http://maven.apache.org/xsd/profiles-1.0.0.xsd";>
dev
true
{code}
Note that the schema for profilesXml is not documented along with settings.xml
and the POM.
http://maven.apache.org/general.html
was:
The documentation at
http://maven.apache.org/guides/introduction/introduction-to-profiles.html seems
to indicate that the schema for profiles.xml is
...
However, it seems that now a root element of ... is
required. A sample working profiles.xml file looks like:
http://maven.apache.org/PROFILES/1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/PROFILES/1.0.0
http://maven.apache.org/xsd/profiles-1.0.0.xsd";>
dev
true
Note that the schema for profilesXml is not documented along with settings.xml
and the POM.
http://maven.apache.org/general.html
> Misleading documentation on the schema of profiles.xml
> --
>
> Key: MNGSITE-102
> URL: http://jira.codehaus.org/browse/MNGSITE-102
> Project: Maven 2 Project Web Site
> Issue Type: Improvement
>Reporter: John Cheng
>
> The documentation at
> http://maven.apache.org/guides/introduction/introduction-to-profiles.html
> seems to indicate that the schema for profiles.xml is
> {code:xml}
> ...
> {code}
> However, it seems that now a root element of ...
> is required. A sample working profiles.xml file looks like:
> {code:xml} xmlns="http://maven.apache.org/PROFILES/1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/PROFILES/1.0.0
> http://maven.apache.org/xsd/profiles-1.0.0.xsd";>
>
>
> dev
>
> true
>
>
>
>
>
> {code}
> Note that the schema for profilesXml is not documented along with
> settings.xml and the POM.
> http://maven.apache.org/general.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] Created: (MNG-4795) [regression] Dependencies in forked reactor projects are not resolved when aggregator bound to lifecycle forks
[regression] Dependencies in forked reactor projects are not resolved when aggregator bound to lifecycle forks -- Key: MNG-4795 URL: http://jira.codehaus.org/browse/MNG-4795 Project: Maven 2 & 3 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 3.0-beta-2 Reporter: Benjamin Bentmann Currently, dependency resolution happens only at the beginning of a project build and then only for the current project. This means if the current project happens to bind an aggregator into its lifecycle which forks the lifecycle in a reactor build, any forked project not previously built during the main build will have its dependencies unresolved. -- 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-4795) [regression] Dependencies in forked reactor projects are not resolved when aggregator bound to lifecycle forks
[ http://jira.codehaus.org/browse/MNG-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4795: --- Attachment: MNG-4795.zip Running "mvn package" from the top-level of the attached project fails with a compilation error in the (forked) sub module. > [regression] Dependencies in forked reactor projects are not resolved when > aggregator bound to lifecycle forks > -- > > Key: MNG-4795 > URL: http://jira.codehaus.org/browse/MNG-4795 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0-beta-2 >Reporter: Benjamin Bentmann > Attachments: MNG-4795.zip > > > Currently, dependency resolution happens only at the beginning of a project > build and then only for the current project. This means if the current > project happens to bind an aggregator into its lifecycle which forks the > lifecycle in a reactor build, any forked project not previously built during > the main build will have its dependencies unresolved. -- 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-4795) [regression] Dependencies in forked reactor projects are not resolved when aggregator bound to lifecycle forks
[ http://jira.codehaus.org/browse/MNG-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234224#action_234224 ] Benjamin Bentmann edited comment on MNG-4795 at 9/4/10 2:03 PM: Running "mvn package" from the top-level of the attached project fails with a compilation error due to missing dependency in the (forked) sub module. was (Author: bentmann): Running "mvn package" from the top-level of the attached project fails with a compilation error in the (forked) sub module. > [regression] Dependencies in forked reactor projects are not resolved when > aggregator bound to lifecycle forks > -- > > Key: MNG-4795 > URL: http://jira.codehaus.org/browse/MNG-4795 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0-beta-2 >Reporter: Benjamin Bentmann > Attachments: MNG-4795.zip > > > Currently, dependency resolution happens only at the beginning of a project > build and then only for the current project. This means if the current > project happens to bind an aggregator into its lifecycle which forks the > lifecycle in a reactor build, any forked project not previously built during > the main build will have its dependencies unresolved. -- 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: (MSITE-497) Dependencies not included classpath for multi-level projects when forking reporting
[ http://jira.codehaus.org/browse/MSITE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234225#action_234225 ] Benjamin Bentmann commented on MSITE-497: - bq. To me this sounds like an issue with dependency resolution in Maven core. Indeed (MNG-4795). > Dependencies not included classpath for multi-level projects when forking > reporting > --- > > Key: MSITE-497 > URL: http://jira.codehaus.org/browse/MSITE-497 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0-beta-1 > Environment: Maven 3.0-beta-2 > MacOS 10.6.4/Windows XP SP2 (or possibly SP3) > Mac Java 1.6.0_20/SUN JDK 1.6.0_15 >Reporter: Anders Hammar >Priority: Critical > Attachments: mvn3site-bug.zip, mvn_site_output.txt > > > Executing "mvn site" on a multi-level project, where it hasn't been compiled > first, makes the build fail because the dependencies can't be found (aren't > included on the classpath). > The attached test projects shows this. If run with Maven 2.2.1 it works fine, > with Maven 3.0-beta-2 it fails. I'm also attaching a debug output of this. > To recreate the issue on the project: > mvn clean > mvn site -- 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-4796) add a warning when profiles.xml is used (Maven 2) or detected (Maven 3)
add a warning when profiles.xml is used (Maven 2) or detected (Maven 3)
---
Key: MNG-4796
URL: http://jira.codehaus.org/browse/MNG-4796
Project: Maven 2 & 3
Issue Type: Wish
Components: Profiles
Affects Versions: 3.0-beta-3, 2.2.1
Reporter: Herve Boutemy
since {{profiles.xml}} is not any more supported in Maven 3, adding a warning
in Maven 2 and Maven 3 (or even a failure in Maven 3) would help people know
about it
--
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: (MNGSITE-102) Misleading documentation on the schema of profiles.xml
[
http://jira.codehaus.org/browse/MNGSITE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MNGSITE-102.
-
Resolution: Fixed
Assignee: Herve Boutemy
documentation improved in
[r992666|http://svn.apache.org/viewvc?rev=992666&view=rev]: added links to
descriptors reference (settings.xml and profiles.xml) and a note about
profiles.xml being deprecated in Maven 3
I created MNG-4796 to have a warning in Maven 2 and 3 when this
{{profiles.xml}} file is detected
> Misleading documentation on the schema of profiles.xml
> --
>
> Key: MNGSITE-102
> URL: http://jira.codehaus.org/browse/MNGSITE-102
> Project: Maven 2 Project Web Site
> Issue Type: Improvement
>Reporter: John Cheng
>Assignee: Herve Boutemy
>
> The documentation at
> http://maven.apache.org/guides/introduction/introduction-to-profiles.html
> seems to indicate that the schema for profiles.xml is
> {code:xml}
> ...
> {code}
> However, it seems that now a root element of ...
> is required. A sample working profiles.xml file looks like:
> {code:xml} xmlns="http://maven.apache.org/PROFILES/1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/PROFILES/1.0.0
> http://maven.apache.org/xsd/profiles-1.0.0.xsd";>
>
>
> dev
>
> true
>
>
>
>
>
> {code}
> Note that the schema for profilesXml is not documented along with
> settings.xml and the POM.
> http://maven.apache.org/general.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: (MNGSITE-24) Check site for dead links
[ http://jira.codehaus.org/browse/MNGSITE-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNGSITE-24. Resolution: Fixed Assignee: Herve Boutemy [Doxia Linkcheck 1.1|http://maven.apache.org/doxia/doxia-tools/doxia-linkcheck/index.html] released on august 2010 and added as a profile in site's pom.xml I just used it to check site links and found no problem > Check site for dead links > - > > Key: MNGSITE-24 > URL: http://jira.codehaus.org/browse/MNGSITE-24 > Project: Maven 2 Project Web Site > Issue Type: Improvement >Reporter: Jason van Zyl >Assignee: Herve Boutemy > > We could use the m1 link checking plugin or we can steal a bit of code from > xstream which has some link checking code. -- 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: (MNGSITE-81) Wrong Root Element in profiles.xml examples used
[
http://jira.codehaus.org/browse/MNGSITE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNGSITE-81:
-
Description:
On the Web-Site http://maven.apache.org/pom.html#Profiles there are examples
which use
{code:xml}http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
...{code}
But this will produce an error with Maven 2.1.0 It is needed to change this
into .
was:
On the Web-Site http://maven.apache.org/pom.html#Profiles there are examples
which use
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
...
But this will produce an error with Maven 2.1.0 It is needed to change this
into .
> Wrong Root Element in profiles.xml examples used
>
>
> Key: MNGSITE-81
> URL: http://jira.codehaus.org/browse/MNGSITE-81
> Project: Maven 2 Project Web Site
> Issue Type: Bug
> Environment: All
>Reporter: Karl Heinz Marbaise
>
> On the Web-Site http://maven.apache.org/pom.html#Profiles there are examples
> which use
> {code:xml}http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> ...{code}
> But this will produce an error with Maven 2.1.0 It is needed to change
> this into .
--
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: (MNGSITE-86) Document usage of negation symbol for profile activation (undocumented feature)
[
http://jira.codehaus.org/browse/MNGSITE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNGSITE-86:
-
Description:
Please, document that the negation symbol "!" can be used for profile
activation not only to test the absence of a property. This is currently not
documented on this page:
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
This request goes back to a thread on the Maven user list, cf.
http://www.nabble.com/Undocumented-Feature%3A-Usage-of-negation-for-profile-activation-td23446509.html
In the following I basically quote the original message posted to the forum;
with some extensions to the example. The example can be almost directly added
to the page to document and illustrate how this feature can be used:
Hello,
I just found a---to my best knowledge---undocumented feature and thought I
should share it with the community in the hope that it will made its way into
the Maven documentation.
The feature is that you can use the negation symbol "!" within a profile
activation specifification not only to test the absence of a property but also
within the tag, for instance, to express something like "activate the
profile if the OS family name is _not_ xyz". The following example illustrates
this:
{code:xml}
tools-jar-windows
windows
${java.home}/../lib/tools.jar
tools-jar-unix
unix
!mac os x
${java.home}/../lib/tools.jar
tools-jar-mac
unix
mac os x
${java.home}/../Classes/classes.jar
{code}
So in this example I use !mac os x to specify that the profile
tools-jar-unix should be applied to all UNIX family operating systems
_except_ Mac OS X.
This example was tested with Maven 2.0.9, 2.0.10, 2.1.0 on Windows XP, Linux
(Ubuntu 8.10), and Mac OS X 10.5.6 and it works for all of them. Nice :-)
Cheers,
Thorsten
was:
Please, document that the negation symbol "!" can be used for profile
activation not only to test the absence of a property. This is currently not
documented on this page:
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
This request goes back to a thread on the Maven user list, cf.
http://www.nabble.com/Undocumented-Feature%3A-Usage-of-negation-for-profile-activation-td23446509.html
In the following I basically quote the original message posted to the forum;
with some extensions to the example. The example can be almost directly added
to the page to document and illustrate how this feature can be used:
Hello,
I just found a---to my best knowledge---undocumented feature and thought I
should share it with the community in the hope that it will made its way into
the Maven documentation.
The feature is that you can use the negation symbol "!" within a profile
activation specifification not only to test the absence of a property but also
within the tag, for instance, to express something like "activate the
profile if the OS family name is _not_ xyz". The following example illustrates
this:
tools-jar-windows
windows
${java.home}/../lib/tools.jar
tools-jar-unix
unix
!mac os x
${java.home}/../lib/tools.jar
tools-jar-mac
unix
mac os x
${java.home}/../Classes/classes.jar
So in this example I use !mac os x to specify that the profile
tools-jar-unix should be applied to all UNIX family operating systems
_except_ Mac OS X.
This example was tested with Maven 2.0.9, 2.
[jira] Closed: (MNGSITE-81) Wrong Root Element in profiles.xml examples used
[
http://jira.codehaus.org/browse/MNGSITE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MNGSITE-81.
Resolution: Cannot Reproduce
> Wrong Root Element in profiles.xml examples used
>
>
> Key: MNGSITE-81
> URL: http://jira.codehaus.org/browse/MNGSITE-81
> Project: Maven 2 Project Web Site
> Issue Type: Bug
> Environment: All
>Reporter: Karl Heinz Marbaise
>
> On the Web-Site http://maven.apache.org/pom.html#Profiles there are examples
> which use
> {code:xml}http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> ...{code}
> But this will produce an error with Maven 2.1.0 It is needed to change
> this into .
--
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: (MNGSITE-76) The http://maven.apache.org/development-process.html WebPage has dead/broken links
[ http://jira.codehaus.org/browse/MNGSITE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNGSITE-76. Resolution: Fixed Assignee: Herve Boutemy yes, this page has moved to http://maven.apache.org/maven-1.x/development-process.html I added a redirection in r992670 > The http://maven.apache.org/development-process.html WebPage has dead/broken > links > -- > > Key: MNGSITE-76 > URL: http://jira.codehaus.org/browse/MNGSITE-76 > Project: Maven 2 Project Web Site > Issue Type: Bug > Environment: not applicable >Reporter: Andre Ouellet >Assignee: Herve Boutemy > > The links to "Best Practices Documents" on the "development-process.html " > page of the Maven Website are all dead/broken > Site/Page with broken links -> The > http://maven.apache.org/development-process.html > The following links are broken: >- Branches >- Deprecation >- Distributions >- Release Process > > Has the documents/content moved ? If so the ... page should be updated with > new working links > Has the documents/content been retired ? If so the ... page should reflect > this -- 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-4796) add a warning when profiles.xml is used (Maven 2) or detected (Maven 3)
[
http://jira.codehaus.org/browse/MNG-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4796.
--
Resolution: Fixed
Fix Version/s: 3.0-beta-4
Assignee: Benjamin Bentmann
Done in [r992683|http://svn.apache.org/viewvc?view=revision&revision=992683].
> add a warning when profiles.xml is used (Maven 2) or detected (Maven 3)
> ---
>
> Key: MNG-4796
> URL: http://jira.codehaus.org/browse/MNG-4796
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Profiles
>Affects Versions: 2.2.1, 3.0-beta-3
>Reporter: Herve Boutemy
>Assignee: Benjamin Bentmann
> Fix For: 3.0-beta-4
>
>
> since {{profiles.xml}} is not any more supported in Maven 3, adding a warning
> in Maven 2 and Maven 3 (or even a failure in Maven 3) would help people know
> about it
--
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: (MNGSITE-110) Best practice links broken in development process
[ http://jira.codehaus.org/browse/MNGSITE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNGSITE-110. - Resolution: Duplicate Assignee: Herve Boutemy > Best practice links broken in development process > - > > Key: MNGSITE-110 > URL: http://jira.codehaus.org/browse/MNGSITE-110 > Project: Maven 2 Project Web Site > Issue Type: Bug >Reporter: Michael Osipov >Assignee: Herve Boutemy > > http://maven.apache.org/development-process.html > Hit all four links on the page => 404 -- 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: (MNGSITE-112) Sample mirror settings at http://maven.apache.org/guides/mini/guide-configuring-maven.html contains an outdated link
[ http://jira.codehaus.org/browse/MNGSITE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNGSITE-112. - Resolution: Fixed Assignee: Herve Boutemy done in r992691 thanks for the report > Sample mirror settings at > http://maven.apache.org/guides/mini/guide-configuring-maven.html contains an > outdated link > > > Key: MNGSITE-112 > URL: http://jira.codehaus.org/browse/MNGSITE-112 > Project: Maven 2 Project Web Site > Issue Type: Improvement >Reporter: Stephen Coy >Assignee: Herve Boutemy > > The Australian mirror site that is referenced has not worked in years. It > will only add to user confusion when it fails to work as advertised. -- 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: (MNGSITE-101) Update 5 min tutorial to use archetype:generate
[ http://jira.codehaus.org/browse/MNGSITE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNGSITE-101. - Resolution: Duplicate Assignee: Herve Boutemy > Update 5 min tutorial to use archetype:generate > --- > > Key: MNGSITE-101 > URL: http://jira.codehaus.org/browse/MNGSITE-101 > Project: Maven 2 Project Web Site > Issue Type: Improvement >Reporter: Haikal Saadh >Assignee: Herve Boutemy >Priority: Minor > Attachments: 5min-tutorial-patch.diff > > > (because archetype:create is 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: (MNGSITE-97) Add enabled phases from current pom.xml for auto completion using BASH
[
http://jira.codehaus.org/browse/MNGSITE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNGSITE-97:
-
Description:
I provide a new feature which get all enabled phases from the current pom.xml.
I don't read the parent pom or settings.xml because it's difficult to know
which parent pom is used, and the current configuration (profile activated,
...). And then it's a small tool, my goal was not corrupting the performance of
the bash
{noformat}#!/bin/bash
_m2_make_goals()
{
plugin=$1
mojos=$2
for mojo in $mojos
do
export goals="$goals $plugin:$mojo"
done
}
_m2_add_phases()
{
for phase in `grep -i '' pom.xml | sed 's/\(.*\)<\/phase>/\1/i'`
do
export goals="$goals $phase"
done
}
_m2_complete()
{
local cur goals
COMPREPLY=()
cur=${COMP_WORDS[COMP_CWORD]}
if [ -f pom.xml ]; then
goals='clean compile test install package deploy site
help:effective-pom dependency:tree'
goals=$goals _m2_make_goals "eclipse" "eclipse"
goals=$goals _m2_add_phases
fi
COMPREPLY=($(compgen -W "${goals}" ${cur} | sed 's///g') )
}
complete -F _m2_complete -o filenames mvn{noformat}
was:
I provide a new feature which get all enabled phases from the current pom.xml.
I don't read the parent pom or settings.xml because it's difficult to know
which parent pom is used, and the current configuration (profile activated,
...). And then it's a small tool, my goal was not corrupting the performance of
the bash
#!/bin/bash
_m2_make_goals()
{
plugin=$1
mojos=$2
for mojo in $mojos
do
export goals="$goals $plugin:$mojo"
done
}
_m2_add_phases()
{
for phase in `grep -i '' pom.xml | sed 's/\(.*\)<\/phase>/\1/i'`
do
export goals="$goals $phase"
done
}
_m2_complete()
{
local cur goals
COMPREPLY=()
cur=${COMP_WORDS[COMP_CWORD]}
if [ -f pom.xml ]; then
goals='clean compile test install package deploy site
help:effective-pom dependency:tree'
goals=$goals _m2_make_goals "eclipse" "eclipse"
goals=$goals _m2_add_phases
fi
COMPREPLY=($(compgen -W "${goals}" ${cur} | sed 's///g') )
}
complete -F _m2_complete -o filenames mvn
> Add enabled phases from current pom.xml for auto completion using BASH
> --
>
> Key: MNGSITE-97
> URL: http://jira.codehaus.org/browse/MNGSITE-97
> Project: Maven 2 Project Web Site
> Issue Type: Improvement
>Reporter: Sylvain MOUQUET
>Priority: Minor
>
> I provide a new feature which get all enabled phases from the current
> pom.xml. I don't read the parent pom or settings.xml because it's difficult
> to know which parent pom is used, and the current configuration (profile
> activated, ...). And then it's a small tool, my goal was not corrupting the
> performance of the bash
> {noformat}#!/bin/bash
> _m2_make_goals()
> {
> plugin=$1
> mojos=$2
> for mojo in $mojos
> do
> export goals="$goals $plugin:$mojo"
> done
> }
> _m2_add_phases()
> {
> for phase in `grep -i '' pom.xml | sed
> 's/\(.*\)<\/phase>/\1/i'`
> do
> export goals="$goals $phase"
> done
> }
> _m2_complete()
> {
> local cur goals
> COMPREPLY=()
> cur=${COMP_WORDS[COMP_CWORD]}
> if [ -f pom.xml ]; then
> goals='clean compile test install package deploy site
> help:effective-pom dependency:tree'
> goals=$goals _m2_make_goals "eclipse" "eclipse"
> goals=$goals _m2_add_phases
> fi
> COMPREPLY=($(compgen -W "${goals}" ${cur} | sed 's///g') )
> }
> complete -F _m2_complete -o filenames mvn{noformat}
--
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] Moved: (SCM-573) Dead link to SCM plugin from http://maven.apache.org/scm/index.html
[ http://jira.codehaus.org/browse/SCM-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy moved MNGSITE-111 to SCM-573: --- Complexity: Novice Key: SCM-573 (was: MNGSITE-111) Project: Maven SCM (was: Maven 2 Project Web Site) > Dead link to SCM plugin from http://maven.apache.org/scm/index.html > --- > > Key: SCM-573 > URL: http://jira.codehaus.org/browse/SCM-573 > Project: Maven SCM > Issue Type: Bug >Reporter: Gabriel Falkenberg >Priority: Minor > > There are links to submodules on http://maven.apache.org/scm/index.html The > last submodule link "Maven SCM Plugin" leads to > http://maven.apache.org/plugins/maven-scm-plugin/index.html (404). The > correct URL to the plugin is: > http://maven.apache.org/scm/maven-scm-plugin/index.html > I checked out what I believe is the source for the site but fail to see > what's wrong since the links in the module section should be generated > automatically and since I cannot find any references to > plugins/maven-scm-plugin in the source. Has this perhaps been fixed but not > yet put live on the site? -- 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: (MNGSITE-114) Standard Directory Layout does not mention NOTICE.txt
[ http://jira.codehaus.org/browse/MNGSITE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNGSITE-114. - Resolution: Fixed Assignee: Herve Boutemy done in r992693 > Standard Directory Layout does not mention NOTICE.txt > - > > Key: MNGSITE-114 > URL: http://jira.codehaus.org/browse/MNGSITE-114 > Project: Maven 2 Project Web Site > Issue Type: Bug > Environment: > http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html >Reporter: SebbASF >Assignee: Herve Boutemy >Priority: Minor > > http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html > does not mention NOTICE.txt alongside LICENSE.txt. > It would be helpful if it did. -- 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
