[jira] Created: (MANTTASKS-77) element of settings.xml ignored by artifact:dependencies.
element of settings.xml ignored by artifact:dependencies. --- Key: MANTTASKS-77 URL: http://jira.codehaus.org/browse/MANTTASKS-77 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: dependencies task Affects Versions: 2.0.7 Environment: WinXP Reporter: Davy Toch Attachments: example.zip When true is set in settings.xml, the dependencies are still downloaded from the central M2 repository. Example included. -- 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-2411) Mistake in guide-building-m2.html
[ http://jira.codehaus.org/browse/MNG-2411?page=comments#action_78972 ] Davy Toch commented on MNG-2411: Also it should be added that when building the latest M2 snapshot version from the trunk, it is necessary to add the M2 snapshot repository to ~/.m2/settings.xml, e.g. by adding: apache.snapshots Apache Snapshot Repository http://people.apache.org/repo/m2-snapshot-repository false m2.snapshotbuild m2.snapshotbuild > Mistake in guide-building-m2.html > - > > Key: MNG-2411 > URL: http://jira.codehaus.org/browse/MNG-2411 > Project: Maven 2 > Issue Type: Task > Components: Documentation: Guides >Affects Versions: 2.0.4 > Environment: - >Reporter: Martin Zeltner > Fix For: 2.0.5 > > > Hi, > I think on page > http://maven.apache.org/guides/development/guide-building-m2.html in chapter > "Building Maven with Maven installed" there should be written "cd maven-cli" > and not "cd maven-core". > Cheers, > Martin -- 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-2636) Namespace settings-1.0.0.xsd correct?
Namespace settings-1.0.0.xsd correct? - Key: MNG-2636 URL: http://jira.codehaus.org/browse/MNG-2636 Project: Maven 2 Issue Type: Improvement Components: Settings Affects Versions: 2.0.4 Environment: - Win XP - JDK 1.5 Reporter: Davy Toch Priority: Minor Currently the namespace chosen in the settings XSD is the same as the one chosen in the POM XSD. This causes conflicts e.g. when using XML catalogs to resolve the XSD files (e.g. when using the WTP/XML Catalog support in Eclipse): POM XSD : http://maven.apache.org/maven-v4_0_0.xsd POM example: 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/maven-v4_0_0.xsd";> ... Settings XSD : http://maven.apache.org/xsd/settings-1.0.0.xsd Settings example : 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/settings-1.0.0.xsd";> ... Having one namespace pointing to two different XSD files, depending on whether you're editing a POM or a settings file isn't a good idea. Question : can't the namespace of the settings XSD be changed or would this have too much of an impact on M2 (e.g. when M2 currently uses a namespace aware parser to parse the XML files)? -- 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-2633) Unexpected behaviour settings in POM.xml.
Unexpected behaviour settings in POM.xml. -- Key: MNG-2633 URL: http://jira.codehaus.org/browse/MNG-2633 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Versions: 2.0.4 Environment: - Win XP - JDK 1.5 Reporter: Davy Toch Attachments: pom.xml Included a POM file which defines two repositories : a non-existing one and the central M2 repository. There is no local settings file ~/.m2/setting.xml and the complete folder ~/.m2/repository/junit is deleted. Now if I run 'maven install', I get the following : $mvn install [INFO] Scanning for projects... [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [install] [INFO] Downloading: http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom 145b downloaded [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] No sources to compile [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. Downloading: http://blieblie/junit/junit/3.8.1/junit-3.8.1.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Error transferring file junit:junit:jar:3.8.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), mybidonrepo (http://blieblie) Path to dependency: 1) testgroup:testartifact:jar:1.0-SNAPSHOT 2) junit:junit:jar:3.8.1 Caused by I/O exception: Server returned HTTP response code: 503 for URL: http://blieblie/junit/junit/3.8.1/junit-3.8.1.jar [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 17 seconds [INFO] Finished at: Thu Oct 26 18:53:06 CEST 2006 [INFO] Final Memory: 3M/6M [INFO] Questions: 1. Is it normal that retrieving the artifact (jar) completely fails the build? M2 could still try to connect to http://repo1.maven.org/maven2 to retrieve the artifact. 2. why is the POM file directly retrieved from http://repo1.maven.org/maven2 (no attempt to retrieve it from http://blieblie)? -- 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-2509) M2/ANT : Weird ClassCastException in in macrodef when calling Beanshell scripting.
[ http://jira.codehaus.org/browse/MNG-2509?page=comments#action_77758 ]
Davy Toch commented on MNG-2509:
The problem seems to be fixed since ANT 1.7.0beta3.
> M2/ANT : Weird ClassCastException in in macrodef when calling
> Beanshell scripting.
> --
>
> Key: MNG-2509
> URL: http://jira.codehaus.org/browse/MNG-2509
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks
>Affects Versions: 2.0.4
> Environment: - ANT 1.6.5 (with bsh-2.0b4.jar in ANT_HOME/lib)
> - JDK 1.5
>Reporter: Davy Toch
> Attachments: build.xml, pom.xml
>
>
> Hi,
> In ANT, sometimes more than one artifact is generated from the same
> build file (e.g. myapp.jar, myapp-client.jar, myapp-with-deps.jar).
> If using the M2 plugin for ANT (currently 2.0.4), this would mean
> we would need three POM's for the above 3 artifacts. However, in the
> above case the 3 POM's would be almost identical.
> So I have taken the following approach in order to have only one generic
> POM:
> pom.xml (with ANT tokens _TOKEN_...):
> 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/maven-v4_0_0.xsd";>
> 4.0.0
> be.steria.test
> _TOKEN_ARTIFACTID_
> _TOKEN_PACKAGING_
> 1.5-SNAPSHOT
> Test artifact
>
>
> log4j
> log4j
> 1.2.9
> compile
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
>
> repo_dev
> scp://localhost/m2demo/repo_dev
>
>
>
> build.xml:
>xmlns:m="antlib:org.apache.maven.artifact.ant">
>
>
>
>
>
>
>toFile="[EMAIL PROTECTED]">
>
>
>to="@{artifactId}"/>
>to="@{packaging}"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
> artifactId="myapp-with-deps"/>
>
>
>
>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
> Now if I execute the above, everything works fine, but if I add
[jira] Commented: (MSUREFIRE-174) Result message of Surefire TestNG run with invalid not logical.
[ http://jira.codehaus.org/browse/MSUREFIRE-174?page=comments#action_77570
]
Davy Toch commented on MSUREFIRE-174:
-
Of course I meant 'mvn test' and not 'maven test'.
> Result message of Surefire TestNG run with invalid not logical.
> --
>
> Key: MSUREFIRE-174
> URL: http://jira.codehaus.org/browse/MSUREFIRE-174
> Project: Maven 2.x Surefire Plugin
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.2
> Environment: - WinXP
> - Maven 2.0.4 (with maven-surefire-plugin 2.2)
>Reporter: Davy Toch
> Attachments: m2-testng-example-jdk15.zip
>
>
> When performing a Surefire TestNG run on Java 1.5 annotated test classes with
> pom.xml
> containing an incorrect testng suite configuration (e.g. pointing to
> inexisting file blieblie.xml),
> the run won't fail but instead will generate the following result:
> ---
> T E S T S
> ---
> There are no tests to run.
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> The problem lies in:
> plugins\maven-surefire-plugin\src\main\java\org\apache\maven\plugin\surefire\SurefirePlugin.java
> (lines around line 500)
> if ( suiteXmlFiles != null && suiteXmlFiles.length > 0 )
> {
> if ( testNgArtifact == null )
> {
> throw new MojoExecutionException( "suiteXmlFiles is
> configured, but there is no TestNG dependency" );
> }
> for ( int i = 0; i < suiteXmlFiles.length; i++ )
> {
> File file = suiteXmlFiles[i];
> if ( file.exists() )
> {
> surefireBooter.addTestSuite(
> "org.apache.maven.surefire.testng.TestNGXmlTestSuite",
> new Object[]{file,
> testSourceDirectory.getAbsolutePath()} );
> }
> }
> If file.exists() returns false, then an Exception should be thrown.
> Remark that with JDK1.4 JavaDoc annotated classes, the same problem arises,
> as well as another problem
> indicated in http://jira.codehaus.org/browse/MSUREFIRE-173 .
> An example is included to illustrate the problem (just run 'maven 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] Commented: (MSUREFIRE-173) TestNG JDK1.4 JavaDoc annotated classes never run ... and now I know why.
[ http://jira.codehaus.org/browse/MSUREFIRE-173?page=comments#action_77571
]
Davy Toch commented on MSUREFIRE-173:
-
Of course I meant 'mvn test' and not 'maven test'.
> TestNG JDK1.4 JavaDoc annotated classes never run ... and now I know why.
> -
>
> Key: MSUREFIRE-173
> URL: http://jira.codehaus.org/browse/MSUREFIRE-173
> Project: Maven 2.x Surefire Plugin
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.2
> Environment: - WinXP
> - Maven 2.0.4 (with maven-surefire-plugin 2.2)
>Reporter: Davy Toch
> Attachments: m2-testng-example-jdk14.zip
>
>
> After a day of trying to find out why JDK1.4 JavaDoc annotated test classes
> were never run, I finally found out why:
> In
> maven-surefire\surefire-providers\surefire-testng\src\main\java\org\apache\maven\surefire\testng\TestNGExecutor.java,
> the method testng.runSuitesLocally() is called:
> static void executeTestNG( SurefireTestSuite surefireSuite, String
> testSourceDirectory, XmlSuite suite,
>ReporterManager reporterManager )
> {
> ...
> // TODO: Doesn't find testng.xml based suites when these are un-commented
> // TestNG ~also~ looks for the currentThread context classloader
> // ClassLoader oldClassLoader =
> Thread.currentThread().getContextClassLoader();
> // Thread.currentThread().setContextClassLoader(
> suite.getClass().getClassLoader() );
> testNG.runSuitesLocally();
> //Thread.currentThread().setContextClassLoader( oldClassLoader );
> ...
> }
> However, in the TestNG 5.1 source file org\testng\TestNG.java, only the
> method run() correctly loads the JDK1.4 annotations. So the above class
> should call testng.run() and not testng.runSuitesLocally().
> org\testng\TestNG.java:
> /**
>* Run TestNG.
>*/
> public void run() {
> // lazy scan sourcedirs if needed
> if(isJdk14() || JAVADOC_ANNOTATION_TYPE.equals(m_target)) {
>
> AnnotationConfiguration.getInstance().getAnnotationFinder().addSourceDirs(m_sourceDirs);
> }
> ...
> }
> The problem is also still present in the latest 2.3-SNAPSHOT version of the
> maven-surefire-plugin.
> Included a small example project to illustrate the problem (just run "maven
> 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] Created: (MSUREFIRE-174) Result message of Surefire TestNG run with invalid not logical.
Result message of Surefire TestNG run with invalid not logical.
--
Key: MSUREFIRE-174
URL: http://jira.codehaus.org/browse/MSUREFIRE-174
Project: Maven 2.x Surefire Plugin
Issue Type: Bug
Components: TestNG support
Affects Versions: 2.2
Environment: - WinXP
- Maven 2.0.4 (with maven-surefire-plugin 2.2)
Reporter: Davy Toch
Attachments: m2-testng-example-jdk15.zip
When performing a Surefire TestNG run on Java 1.5 annotated test classes with
pom.xml
containing an incorrect testng suite configuration (e.g. pointing to inexisting
file blieblie.xml),
the run won't fail but instead will generate the following result:
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
The problem lies in:
plugins\maven-surefire-plugin\src\main\java\org\apache\maven\plugin\surefire\SurefirePlugin.java
(lines around line 500)
if ( suiteXmlFiles != null && suiteXmlFiles.length > 0 )
{
if ( testNgArtifact == null )
{
throw new MojoExecutionException( "suiteXmlFiles is configured,
but there is no TestNG dependency" );
}
for ( int i = 0; i < suiteXmlFiles.length; i++ )
{
File file = suiteXmlFiles[i];
if ( file.exists() )
{
surefireBooter.addTestSuite(
"org.apache.maven.surefire.testng.TestNGXmlTestSuite",
new Object[]{file,
testSourceDirectory.getAbsolutePath()} );
}
}
If file.exists() returns false, then an Exception should be thrown.
Remark that with JDK1.4 JavaDoc annotated classes, the same problem arises, as
well as another problem
indicated in http://jira.codehaus.org/browse/MSUREFIRE-173 .
An example is included to illustrate the problem (just run 'maven 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] Created: (MSUREFIRE-173) TestNG JDK1.4 JavaDoc annotated classes never run ... and now I know why.
TestNG JDK1.4 JavaDoc annotated classes never run ... and now I know why.
-
Key: MSUREFIRE-173
URL: http://jira.codehaus.org/browse/MSUREFIRE-173
Project: Maven 2.x Surefire Plugin
Issue Type: Bug
Components: TestNG support
Affects Versions: 2.2
Environment: - WinXP
- Maven 2.0.4 (with maven-surefire-plugin 2.2)
Reporter: Davy Toch
Attachments: m2-testng-example-jdk14.zip
After a day of trying to find out why JDK1.4 JavaDoc annotated test classes
were never run, I finally found out why:
In
maven-surefire\surefire-providers\surefire-testng\src\main\java\org\apache\maven\surefire\testng\TestNGExecutor.java,
the method testng.runSuitesLocally() is called:
static void executeTestNG( SurefireTestSuite surefireSuite, String
testSourceDirectory, XmlSuite suite,
ReporterManager reporterManager )
{
...
// TODO: Doesn't find testng.xml based suites when these are un-commented
// TestNG ~also~ looks for the currentThread context classloader
// ClassLoader oldClassLoader =
Thread.currentThread().getContextClassLoader();
// Thread.currentThread().setContextClassLoader(
suite.getClass().getClassLoader() );
testNG.runSuitesLocally();
//Thread.currentThread().setContextClassLoader( oldClassLoader );
...
}
However, in the TestNG 5.1 source file org\testng\TestNG.java, only the method
run() correctly loads the JDK1.4 annotations. So the above class should call
testng.run() and not testng.runSuitesLocally().
org\testng\TestNG.java:
/**
* Run TestNG.
*/
public void run() {
// lazy scan sourcedirs if needed
if(isJdk14() || JAVADOC_ANNOTATION_TYPE.equals(m_target)) {
AnnotationConfiguration.getInstance().getAnnotationFinder().addSourceDirs(m_sourceDirs);
}
...
}
The problem is also still present in the latest 2.3-SNAPSHOT version of the
maven-surefire-plugin.
Included a small example project to illustrate the problem (just run "maven
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] Closed: (MNG-2358) Default value for 'file' attribute of install/deploy tasks should be available.
[ http://jira.codehaus.org/browse/MNG-2358?page=all ]
Davy Toch closed MNG-2358.
--
Resolution: Won't Fix
Fix Version/s: (was: 2.1)
Closed because based I misinterpreted the documentation for the M2 ANT tasks.
> Default value for 'file' attribute of install/deploy tasks should be
> available.
> ---
>
> Key: MNG-2358
> URL: http://jira.codehaus.org/browse/MNG-2358
> Project: Maven 2
> Issue Type: Improvement
> Components: Ant tasks
>Affects Versions: 2.0.4
> Environment: Not of importance.
>Reporter: Davy Toch
>
> It would be useful to have a default value for the 'file' attribute in the
> install/deploy tasks of the M2 ant tasks, based on the POM settings.
>xmlns:m="antlib:org.apache.maven.artifact.ant">
>
> ...
>
>
>
> value="${POM.build.directory}/${POM.artifactId}-${POM.version}.${POM.packaging}"/>
> ...
>
>
>
>
>
>
>
>
--
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-2509) M2/ANT : Weird ClassCastException in in macrodef when calling Beanshell scripting.
[ http://jira.codehaus.org/browse/MNG-2509?page=comments#action_76957 ] Davy Toch commented on MNG-2509: Apparently the problem is known and can be solved by a hack using the attribute setbeans="false" on
[jira] Commented: (MNG-2509) M2/ANT : Weird ClassCastException in in macrodef when calling Beanshell scripting.
[ http://jira.codehaus.org/browse/MNG-2509?page=comments#action_75166 ]
Davy Toch commented on MNG-2509:
Also tried it with ANT 1.7.0Beta2 but unfortunately the same problem arises.
> M2/ANT : Weird ClassCastException in in macrodef when calling
> Beanshell scripting.
> --
>
> Key: MNG-2509
> URL: http://jira.codehaus.org/browse/MNG-2509
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks
>Affects Versions: 2.0.4
> Environment: - ANT 1.6.5 (with bsh-2.0b4.jar in ANT_HOME/lib)
> - JDK 1.5
>Reporter: Davy Toch
> Attachments: build.xml, pom.xml
>
>
> Hi,
> In ANT, sometimes more than one artifact is generated from the same
> build file (e.g. myapp.jar, myapp-client.jar, myapp-with-deps.jar).
> If using the M2 plugin for ANT (currently 2.0.4), this would mean
> we would need three POM's for the above 3 artifacts. However, in the
> above case the 3 POM's would be almost identical.
> So I have taken the following approach in order to have only one generic
> POM:
> pom.xml (with ANT tokens _TOKEN_...):
> 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/maven-v4_0_0.xsd";>
> 4.0.0
> be.steria.test
> _TOKEN_ARTIFACTID_
> _TOKEN_PACKAGING_
> 1.5-SNAPSHOT
> Test artifact
>
>
> log4j
> log4j
> 1.2.9
> compile
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
>
> repo_dev
> scp://localhost/m2demo/repo_dev
>
>
>
> build.xml:
>xmlns:m="antlib:org.apache.maven.artifact.ant">
>
>
>
>
>
>
>toFile="[EMAIL PROTECTED]">
>
>
>to="@{artifactId}"/>
>to="@{packaging}"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
> artifactId="myapp-with-deps"/>
>
>
>
>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
> Now if I execute the above, everything works fine, but if I add
[jira] Commented: (MNG-2509) M2/ANT : Weird ClassCastException in in macrodef when calling Beanshell scripting.
[ http://jira.codehaus.org/browse/MNG-2509?page=comments#action_75137 ]
Davy Toch commented on MNG-2509:
Tried it with ANT 1.7.0Beta1 but unfortunately same problem. Will try it with
1.7.0Beta2 once the Apache site is up again.
> M2/ANT : Weird ClassCastException in in macrodef when calling
> Beanshell scripting.
> --
>
> Key: MNG-2509
> URL: http://jira.codehaus.org/browse/MNG-2509
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks
>Affects Versions: 2.0.4
> Environment: - ANT 1.6.5 (with bsh-2.0b4.jar in ANT_HOME/lib)
> - JDK 1.5
>Reporter: Davy Toch
> Attachments: build.xml, pom.xml
>
>
> Hi,
> In ANT, sometimes more than one artifact is generated from the same
> build file (e.g. myapp.jar, myapp-client.jar, myapp-with-deps.jar).
> If using the M2 plugin for ANT (currently 2.0.4), this would mean
> we would need three POM's for the above 3 artifacts. However, in the
> above case the 3 POM's would be almost identical.
> So I have taken the following approach in order to have only one generic
> POM:
> pom.xml (with ANT tokens _TOKEN_...):
> 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/maven-v4_0_0.xsd";>
> 4.0.0
> be.steria.test
> _TOKEN_ARTIFACTID_
> _TOKEN_PACKAGING_
> 1.5-SNAPSHOT
> Test artifact
>
>
> log4j
> log4j
> 1.2.9
> compile
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
>
> repo_dev
> scp://localhost/m2demo/repo_dev
>
>
>
> build.xml:
>xmlns:m="antlib:org.apache.maven.artifact.ant">
>
>
>
>
>
>
>toFile="[EMAIL PROTECTED]">
>
>
>to="@{artifactId}"/>
>to="@{packaging}"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
> artifactId="myapp-with-deps"/>
>
>
>
>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
> Now if I execute the above, everything works fine, but if I add
[jira] Created: (MNG-2540) M2 website : move content of "Examples" link to "Guides" link.
M2 website : move content of "Examples" link to "Guides" link. -- Key: MNG-2540 URL: http://jira.codehaus.org/browse/MNG-2540 Project: Maven 2 Issue Type: Improvement Components: Documentation: General Reporter: Davy Toch Priority: Minor On http://maven.apache.org/examples/index.html there is only one example "Injecting POM properties via settings.xml", which could be put on : http://maven.apache.org/guides/index.html This would allow the 'examples' link in the left menu to be deleted. -- 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-2538) Improve plugin documentation on http://maven.apache.org/plugins/index.html.
Improve plugin documentation on http://maven.apache.org/plugins/index.html. --- Key: MNG-2538 URL: http://jira.codehaus.org/browse/MNG-2538 Project: Maven 2 Issue Type: Improvement Components: Documentation: General Reporter: Davy Toch Priority: Minor On http://maven.apache.org/plugins/index.html, the following text is available: "To see the most up-to-date list of available plugins, browse the Maven 2 plugin repository at http://www.ibiblio.org/maven2/."; However in this folder you have: 1. maven-plugins : apparently contains only M1 plugins 2. plugins : contains base M2 plugins and one codehaus plugin 3. plugin : empty, so can be deleted 4. maven-torque-plugin : only metadata files, so can be deleted 5. maven-xdoclet2-plugin : empty, so can be deleted To avoid confusion for novice M2 users, I think it's best to: a. delete the unnecessary folders (3, 4, 5) b. document in the website that "http://www.ibiblio.org/maven2/plugins"; should be verified for the latest versions of M2 plugins instead of "http://www.ibiblio.org/maven2";. c. add a remark to state that "http://www.ibiblio.org/maven2/maven-plugins"; is only for M1 and should be ignored for M2. -- 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-1058) Incorrect POM for xdoclet-bea-module.
Incorrect POM for xdoclet-bea-module. - Key: MAVENUPLOAD-1058 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1058 Project: maven-upload-requests Issue Type: Improvement Reporter: Davy Toch The POM should also include a dependency to xdoclet-web-module. -- 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-2509) M2/ANT : Weird ClassCastException in in macrodef when calling Beanshell scripting.
[ http://jira.codehaus.org/browse/MNG-2509?page=all ]
Davy Toch updated MNG-2509:
---
Attachment: pom.xml
> M2/ANT : Weird ClassCastException in in macrodef when calling
> Beanshell scripting.
> --
>
> Key: MNG-2509
> URL: http://jira.codehaus.org/browse/MNG-2509
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks
>Affects Versions: 2.0.4
> Environment: - ANT 1.6.5 (with bsh-2.0b4.jar in ANT_HOME/lib)
> - JDK 1.5
>Reporter: Davy Toch
> Attachments: build.xml, pom.xml
>
>
> Hi,
> In ANT, sometimes more than one artifact is generated from the same
> build file (e.g. myapp.jar, myapp-client.jar, myapp-with-deps.jar).
> If using the M2 plugin for ANT (currently 2.0.4), this would mean
> we would need three POM's for the above 3 artifacts. However, in the
> above case the 3 POM's would be almost identical.
> So I have taken the following approach in order to have only one generic
> POM:
> pom.xml (with ANT tokens _TOKEN_...):
> 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/maven-v4_0_0.xsd";>
> 4.0.0
> be.steria.test
> _TOKEN_ARTIFACTID_
> _TOKEN_PACKAGING_
> 1.5-SNAPSHOT
> Test artifact
>
>
> log4j
> log4j
> 1.2.9
> compile
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
>
> repo_dev
> scp://localhost/m2demo/repo_dev
>
>
>
> build.xml:
>xmlns:m="antlib:org.apache.maven.artifact.ant">
>
>
>
>
>
>
>toFile="[EMAIL PROTECTED]">
>
>
>to="@{artifactId}"/>
>to="@{packaging}"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
> artifactId="myapp-with-deps"/>
>
>
>
>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
> Now if I execute the above, everything works fine, but if I add
[jira] Updated: (MNG-2509) M2/ANT : Weird ClassCastException in in macrodef when calling Beanshell scripting.
[ http://jira.codehaus.org/browse/MNG-2509?page=all ]
Davy Toch updated MNG-2509:
---
Attachment: build.xml
> M2/ANT : Weird ClassCastException in in macrodef when calling
> Beanshell scripting.
> --
>
> Key: MNG-2509
> URL: http://jira.codehaus.org/browse/MNG-2509
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks
>Affects Versions: 2.0.4
> Environment: - ANT 1.6.5 (with bsh-2.0b4.jar in ANT_HOME/lib)
> - JDK 1.5
>Reporter: Davy Toch
> Attachments: build.xml, pom.xml
>
>
> Hi,
> In ANT, sometimes more than one artifact is generated from the same
> build file (e.g. myapp.jar, myapp-client.jar, myapp-with-deps.jar).
> If using the M2 plugin for ANT (currently 2.0.4), this would mean
> we would need three POM's for the above 3 artifacts. However, in the
> above case the 3 POM's would be almost identical.
> So I have taken the following approach in order to have only one generic
> POM:
> pom.xml (with ANT tokens _TOKEN_...):
> 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/maven-v4_0_0.xsd";>
> 4.0.0
> be.steria.test
> _TOKEN_ARTIFACTID_
> _TOKEN_PACKAGING_
> 1.5-SNAPSHOT
> Test artifact
>
>
> log4j
> log4j
> 1.2.9
> compile
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
>
> repo_dev
> scp://localhost/m2demo/repo_dev
>
>
>
> build.xml:
>xmlns:m="antlib:org.apache.maven.artifact.ant">
>
>
>
>
>
>
>toFile="[EMAIL PROTECTED]">
>
>
>to="@{artifactId}"/>
>to="@{packaging}"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
> artifactId="myapp-with-deps"/>
>
>
>
>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
> Now if I execute the above, everything works fine, but if I add
[jira] Created: (MNG-2509) M2/ANT : Weird ClassCastException in in macrodef when calling Beanshell scripting.
M2/ANT : Weird ClassCastException in in macrodef when calling Beanshell scripting. -- Key: MNG-2509 URL: http://jira.codehaus.org/browse/MNG-2509 Project: Maven 2 Issue Type: Bug Components: Ant tasks Affects Versions: 2.0.4 Environment: - ANT 1.6.5 (with bsh-2.0b4.jar in ANT_HOME/lib) - JDK 1.5 Reporter: Davy Toch Hi, In ANT, sometimes more than one artifact is generated from the same build file (e.g. myapp.jar, myapp-client.jar, myapp-with-deps.jar). If using the M2 plugin for ANT (currently 2.0.4), this would mean we would need three POM's for the above 3 artifacts. However, in the above case the 3 POM's would be almost identical. So I have taken the following approach in order to have only one generic POM: pom.xml (with ANT tokens _TOKEN_...): 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/maven-v4_0_0.xsd";> 4.0.0 be.steria.test _TOKEN_ARTIFACTID_ _TOKEN_PACKAGING_ 1.5-SNAPSHOT Test artifact log4j log4j 1.2.9 compile junit junit 3.8.1 test repo_dev scp://localhost/m2demo/repo_dev build.xml: Now if I execute the above, everything works fine, but if I add in the target 'm2init', then the following error is generated on the first call: "java.lang.ClassCastException: org.apache.maven.artifact.ant.Pom" Regards, Davy Toch -- 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-2359) ~/.m2/settings.xml ignored when using M2 ant task 'install-provider'
[ http://jira.codehaus.org/browse/MNG-2359?page=all ] Davy Toch closed MNG-2359: -- Resolution: Duplicate Duplicate of MNG-2360 (entered case 2 times by accident). > ~/.m2/settings.xml ignored when using M2 ant task 'install-provider' > > > Key: MNG-2359 > URL: http://jira.codehaus.org/browse/MNG-2359 > Project: Maven 2 > Type: Bug > Reporter: Davy Toch > > > From the local M2 repository I deleted the jar file junit 3.8.1 > including the corresponding POM and hash files. However these files are > also present in our corporate repository (currently used for simulation > purposes): > http://localhost:8080/maven-proxy-webapp/repository > We also have a file ~/.m2/settings.xml: > > > > central > central_mirror > http://localhost:8080/maven-proxy-webapp/repository > > > > > DEV > > > central > http://localhost:8080/maven-proxy-webapp/repository > > > > > > false > > central > http://localhost:8080/maven-proxy-webapp/repository > > > > repo_dev > scp://localhost/m2demo/repo_dev > > > > > DEV > > > This allows to always pass through the corporate repository to retrieve > artifacts/plugins (instead of the default repository > http://www.ibiblio.org/maven2). > Remark that this corporate repository is running locally , so normally > it is NOT needed to have Internet access. **Therefore the local machine > isn't connected to the Internet.** > We have the following ANT script build.xml that uses M2 ant tasks 2.0.4: > build.xml: >xmlns:m="antlib:org.apache.maven.artifact.ant"> > >version="1.0-alpha-5"/> > > > In the same folder as build.xml we also have a file pom.xml: > > 4.0.0 > com.mycompany.project > project-model > 1.0-SNAPSHOT > > > junit > junit > 3.8.1 > compile > > > commons-collections > commons-collections > 2.0 > provided > > > > > repo_dev > scp://localhost/m2demo/repo_dev > > > > When executing the target 'test' from the above ANT script, we get the > following error message: > test: > [m:install-provider] An error has occurred while processing the Maven > artifact tasks. > [m:install-provider] Diagnosis: > [m:install-provider] > [m:install-provider] Error downloading wagon provider from the remote > repository: Unable to get dependency information: Unable to read the > metadata file for artifact 'junit:junit:jar': Error getting P OM for > 'junit:junit' from the repository: Error transferring file > [m:install-provider] junit:junit:pom:3.8.1 > [m:install-provider] > [m:install-provider] from the specified remote repositories: > [m:install-provider] central (http://repo1.maven.org/maven2) > [m:install-provider] > [m:install-provider] junit:junit:jar:3.8.1 > [m:install-provider] > [m:install-provider] from the specified remote repositories: > [m:install-provider] central (http://repo1.maven.org/maven2) > [m:install-provider] Path to dependency: > [m:install-provider]1) unspecified:unspecified:jar:0.0 > [m:install-provider]2) org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 > [m:install-provider]3) > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 > [m:install-provider] > [m:install-provider] > [m:install-provider] > BUILD FAILED > C:\tmp\build.xml:8: Error downloading wagon provider from the remote > repository: Unable to get dependency information: Unable to read the > metadata file for artifact 'junit:junit:jar': Error getting PO M for > 'junit:junit' from the repository: Error transferring file > junit:junit:pom:3.8.1 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > junit:junit:jar:3.8.1 > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > Path to dependency: > 1) unspecified:unspecified:jar:0.0 > 2) org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 > 3) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 > So it seems just ignores the central repository > settings defined in ~/.m2/settings.xml and uses the settings defined in > wagon-ssh-1.0-alpha-5.pom instead. > Remark : we also tested with the following variants of the above ANT > script build.xml: >xmlns:m="antlib:org.apache.maven.artifact.ant"> > > >version="1.0-alpha-5"/> > > > > but unfortunately the same error occurred. > However, the following ANT script solves the above problem : >xmlns:m="antlib:org.apache.maven.artifact.ant"> > > > > > >version="1.0-alpha-5"/> > > > but this is because the task correctly use
[jira] Created: (MNG-2361) Document pomRefId attribute for M2 ant tasks on M2 website.
Document pomRefId attribute for M2 ant tasks on M2 website. --- Key: MNG-2361 URL: http://jira.codehaus.org/browse/MNG-2361 Project: Maven 2 Type: Wish Components: Ant tasks Versions: 2.0.4 Environment: Not of importance. Reporter: Davy Toch Priority: Minor Consider the following ANT script: The following **undocumented** shorthand notation is available: The shorter, the better :-). -- 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-2360) ~/.m2/settings.xml ignored when using M2 ant task 'install-provider'
~/.m2/settings.xml ignored when using M2 ant task 'install-provider' Key: MNG-2360 URL: http://jira.codehaus.org/browse/MNG-2360 Project: Maven 2 Type: Bug Components: Ant tasks Versions: 2.0.4 Environment: Windows XP SP2. Reporter: Davy Toch >From the local M2 repository I deleted the jar file junit 3.8.1 including the corresponding POM and hash files. However these files are also present in our corporate repository (currently used for simulation purposes): http://localhost:8080/maven-proxy-webapp/repository We also have a file ~/.m2/settings.xml: central central_mirror http://localhost:8080/maven-proxy-webapp/repository DEV central http://localhost:8080/maven-proxy-webapp/repository false central http://localhost:8080/maven-proxy-webapp/repository repo_dev scp://localhost/m2demo/repo_dev DEV This allows to always pass through the corporate repository to retrieve artifacts/plugins (instead of the default repository http://www.ibiblio.org/maven2). Remark that this corporate repository is running locally , so normally it is NOT needed to have Internet access. **Therefore the local machine isn't connected to the Internet.** We have the following ANT script build.xml that uses M2 ant tasks 2.0.4: build.xml: In the same folder as build.xml we also have a file pom.xml: 4.0.0 com.mycompany.project project-model 1.0-SNAPSHOT junit junit 3.8.1 compile commons-collections commons-collections 2.0 provided repo_dev scp://localhost/m2demo/repo_dev When executing the target 'test' from the above ANT script, we get the following error message: test: [m:install-provider] An error has occurred while processing the Maven artifact tasks. [m:install-provider] Diagnosis: [m:install-provider] [m:install-provider] Error downloading wagon provider from the remote repository: Unable to get dependency information: Unable to read the metadata file for artifact 'junit:junit:jar': Error getting P OM for 'junit:junit' from the repository: Error transferring file [m:install-provider] junit:junit:pom:3.8.1 [m:install-provider] [m:install-provider] from the specified remote repositories: [m:install-provider] central (http://repo1.maven.org/maven2) [m:install-provider] [m:install-provider] junit:junit:jar:3.8.1 [m:install-provider] [m:install-provider] from the specified remote repositories: [m:install-provider] central (http://repo1.maven.org/maven2) [m:install-provider] Path to dependency: [m:install-provider]1) unspecified:unspecified:jar:0.0 [m:install-provider]2) org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 [m:install-provider]3) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 [m:install-provider] [m:install-provider] [m:install-provider] BUILD FAILED C:\tmp\build.xml:8: Error downloading wagon provider from the remote repository: Unable to get dependency information: Unable to read the metadata file for artifact 'junit:junit:jar': Error getting PO M for 'junit:junit' from the repository: Error transferring file junit:junit:pom:3.8.1 from the specified remote repositories: central (http://repo1.maven.org/maven2) junit:junit:jar:3.8.1 from the specified remote repositories: central (http://repo1.maven.org/maven2) Path to dependency: 1) unspecified:unspecified:jar:0.0 2) org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 3) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 So it seems install-provider just ignores the central repository settings defined in ~/.m2/settings.xml and uses the settings defined in wagon-ssh-1.0-alpha-5.pom . Remark : we also tested with the following variants of the above ANT script build.xml: but unfortunately the same error occurred. However, the following ANT script solves the above problem : but this is because the task m:dependencies correctly uses the file ~/.m2/settings.xml to retrieve junit from the corporate 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] Created: (MNG-2359) ~/.m2/settings.xml ignored when using M2 ant task 'install-provider'
~/.m2/settings.xml ignored when using M2 ant task 'install-provider' Key: MNG-2359 URL: http://jira.codehaus.org/browse/MNG-2359 Project: Maven 2 Type: Bug Reporter: Davy Toch >From the local M2 repository I deleted the jar file junit 3.8.1 including the corresponding POM and hash files. However these files are also present in our corporate repository (currently used for simulation purposes): http://localhost:8080/maven-proxy-webapp/repository We also have a file ~/.m2/settings.xml: central central_mirror http://localhost:8080/maven-proxy-webapp/repository DEV central http://localhost:8080/maven-proxy-webapp/repository false central http://localhost:8080/maven-proxy-webapp/repository repo_dev scp://localhost/m2demo/repo_dev DEV This allows to always pass through the corporate repository to retrieve artifacts/plugins (instead of the default repository http://www.ibiblio.org/maven2). Remark that this corporate repository is running locally , so normally it is NOT needed to have Internet access. **Therefore the local machine isn't connected to the Internet.** We have the following ANT script build.xml that uses M2 ant tasks 2.0.4: build.xml: In the same folder as build.xml we also have a file pom.xml: 4.0.0 com.mycompany.project project-model 1.0-SNAPSHOT junit junit 3.8.1 compile commons-collections commons-collections 2.0 provided repo_dev scp://localhost/m2demo/repo_dev When executing the target 'test' from the above ANT script, we get the following error message: test: [m:install-provider] An error has occurred while processing the Maven artifact tasks. [m:install-provider] Diagnosis: [m:install-provider] [m:install-provider] Error downloading wagon provider from the remote repository: Unable to get dependency information: Unable to read the metadata file for artifact 'junit:junit:jar': Error getting P OM for 'junit:junit' from the repository: Error transferring file [m:install-provider] junit:junit:pom:3.8.1 [m:install-provider] [m:install-provider] from the specified remote repositories: [m:install-provider] central (http://repo1.maven.org/maven2) [m:install-provider] [m:install-provider] junit:junit:jar:3.8.1 [m:install-provider] [m:install-provider] from the specified remote repositories: [m:install-provider] central (http://repo1.maven.org/maven2) [m:install-provider] Path to dependency: [m:install-provider]1) unspecified:unspecified:jar:0.0 [m:install-provider]2) org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 [m:install-provider]3) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 [m:install-provider] [m:install-provider] [m:install-provider] BUILD FAILED C:\tmp\build.xml:8: Error downloading wagon provider from the remote repository: Unable to get dependency information: Unable to read the metadata file for artifact 'junit:junit:jar': Error getting PO M for 'junit:junit' from the repository: Error transferring file junit:junit:pom:3.8.1 from the specified remote repositories: central (http://repo1.maven.org/maven2) junit:junit:jar:3.8.1 from the specified remote repositories: central (http://repo1.maven.org/maven2) Path to dependency: 1) unspecified:unspecified:jar:0.0 2) org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 3) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 So it seems just ignores the central repository settings defined in ~/.m2/settings.xml and uses the settings defined in wagon-ssh-1.0-alpha-5.pom instead. Remark : we also tested with the following variants of the above ANT script build.xml: but unfortunately the same error occurred. However, the following ANT script solves the above problem : but this is because the task correctly uses the file ~/.m2/settings.xml to retrieve junit from the corporate 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] Created: (MNG-2358) Default value for 'file' attribute of install/deploy tasks should be available.
Default value for 'file' attribute of install/deploy tasks should be available. --- Key: MNG-2358 URL: http://jira.codehaus.org/browse/MNG-2358 Project: Maven 2 Type: Improvement Components: Ant tasks Versions: 2.0.4 Environment: Not of importance. Reporter: Davy Toch It would be useful to have a default value for the 'file' attribute in the install/deploy tasks of the M2 ant tasks, based on the POM settings. ... ... -- 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-34) Option to set deployed artifact read-only should be added.
Option to set deployed artifact read-only should be added. -- Key: MDEPLOY-34 URL: http://jira.codehaus.org/browse/MDEPLOY-34 Project: Maven 2.x Deploy Plugin Type: Improvement Environment: Not of importance. Reporter: Davy Toch Fix For: 2.3 It would be useful for non-SNAPSHOT artifacts to have an option that allows to set the artifact read-only on the remote repository to avoid that stable versions are overridden by accident. -- 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
