[jira] Created: (MNG-4927) profile activation have trouble when based on project variable
profile activation have trouble when based on project variable
--
Key: MNG-4927
URL: http://jira.codehaus.org/browse/MNG-4927
Project: Maven 2 3
Issue Type: Bug
Affects Versions: 3.0.1, 2.2.1
Environment: Ubuntu/Maven 3.0.1 or WindowsXP/Maven 2.2.1
JVM 1.6
Reporter: David N'DIAYE
Attachments: pom.xml
I tried to manage the generation of Java code from a wsdl via a Maven profile
that is activated only if the build directory does not exist, and the
activation profile behaved oddly.
For example, this activation code is always active, even if
{{'target/generated-sources'}} exists.
{code:xml}
activation
activeByDefaultfalse/activeByDefault
file
missing${project.build.directory}/generated-sources//missing
/file
/activation
{code}
I create a simple test case.
# first step, check profiles which are activate
{code:title=mvn help:active-profiles|borderStyle=solid}
$ mvn help:active-profiles
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building profile 0.0.1
[INFO]
[INFO]
[INFO] --- maven-help-plugin:2.1.1:active-profiles (default-cli) @ profile ---
[INFO]
Active Profiles for Project 'tescase:profile:jar:0.0.1':
The following profiles are active:
- test-profile-ok (source: pom)
- test-profile-ko (source: pom)
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{code}
# second step, compile
{code:title=mvn compile|borderStyle=solid}
$ mvn compile
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building profile 0.0.1
[INFO]
[INFO]
[INFO] --- maven-antrun-plugin:1.3:run (wsdl2java-ko) @ profile ---
[INFO] Executing tasks
[echo] profile test-profile-ko : unfortunately this profile is always
active
[INFO] Executed tasks
[INFO]
[INFO] --- maven-antrun-plugin:1.3:run (wsdl2java-ok) @ profile ---
[INFO] Executing tasks
[echo] profile test-profile-ok : This profile is active if and only if,
the directory 'target/generated-sources' does not exist
[INFO] Executed tasks
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ profile
---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/home/david/tmp/jira/maven/activationProfile/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ profile ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-antrun-plugin:1.3:run (default) @ profile ---
[INFO] Executing tasks
[echo] build sample
[echo] mkdir
/home/david/tmp/jira/maven/activationProfile/target/generated-sources
[mkdir] Created dir:
/home/david/tmp/jira/maven/activationProfile/target/generated-sources
[INFO] Executed tasks
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{code}
# third step : the first error, *{color:red}the profile which is activate by
variable is always active{color}*
{code:title=mvn help:active-profiles|borderStyle=solid}
$ mvn help:active-profiles
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building profile 0.0.1
[INFO]
[INFO]
[INFO] --- maven-help-plugin:2.1.1:active-profiles (default-cli) @ profile ---
[INFO]
Active Profiles for Project 'tescase:profile:jar:0.0.1':
The following profiles are active:
- test-profile-ko (source: pom)
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{code}
# fourth step : when i relaunch the compile *{color:red}the profile is still
active{color}*
{code:title=mvn compile|borderStyle=solid}
$ mvn compile
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building profile 0.0.1
[INFO]
[INFO]
[INFO]
[jira] Created: (MANTTASKS-91) [task dependencies]Trouble between mvn and manttasks
[task dependencies]Trouble between mvn and manttasks
Key: MANTTASKS-91
URL: http://jira.codehaus.org/browse/MANTTASKS-91
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: dependencies task
Affects Versions: 2.0.7
Environment: Windows 2000/XP
Java version: 1.4.2_03
Ant 1.6.5
Reporter: David N'DIAYE
Attachments: testDependency.zip
I have a library {{org.test.b}}.
* In the first version i declare i have a dependency with the library
{{org.test:d:1.1}}
* In the second version i declare i have no dependencies
My current developpement use the library {{org.test.a}} which have a dependency
with {{org.test:b:1.0}}.
I declare i prefered to use the new library {{org.test:b:1.1}}
and i have another library {{org.test:c}} because of its dependency, it must
use the library {{org.test:d}}
If i write my pom like this :
{code:xml}dependencies
dependency
groupIdorg.test/groupId
artifactIda/artifactId
version1.0/version
/dependency
dependency
groupIdorg.test/groupId
artifactIdc/artifactId
version1.0/version
/dependency
dependency
groupIdorg.test/groupId
artifactIdb/artifactId
version1.1/version
/dependency
/dependencies
{code}
When I run ant with this pom :
{code:xml}
artifact:pom id=pom file=pom.xml /
artifact:remoteRepository id=repository url=file:./repository /
artifact:dependencies filesetId=compile.dependency.fileset
useScope=compile verbose=true
pom refid=pom /
remoteRepository refid=repository /
localRepository path=./localRepository /
/artifact:dependencies
{code}
*{color:red}the dependency fileset does not contain the library
{{org.test:d}}{color}*
And when i run *{{mvn site:site}}*, {color:green}i have {{org.test:d:1.2}} in
the scope compile{color}.
-
here, you can find the dependency tree of my testcase
{noformat}
test:test-tree:jar:1.0 (selected)
org.test:a:jar:1.0:compile (selected)
org.test:b:jar:1.0:compile (selected)
org.test:d:jar:1.1:compile (selected)
org.test:c:jar:1.0:compile (selected)
org.test:e:jar:1.0:compile (selected)
org.test:d:jar:1.2:compile (removed - nearer found: 1.1)
org.test:b:jar:1.0:compile (removed - nearer found: 1.1)
org.test:b:jar:1.1:compile (selected)
{noformat}
To run my testcase you can do :
* {{ant clean}} : to remove all generated
* {{ant test}} : to check the problem
And you run maven (2.0.7) like this :
* {{mvn -s settings.xml site: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: (MANTTASKS-73) miss RemoteRepository sub-element for tasks pom and install-provider
miss RemoteRepository sub-element for tasks pom and install-provider
Key: MANTTASKS-73
URL: http://jira.codehaus.org/browse/MANTTASKS-73
Project: Maven 2.x Ant Tasks
Issue Type: Wish
Components: install-provider task, POM Integration
Affects Versions: 2.0.7
Environment: Ant 1.6.5 / Maven Ant Task 2.0.6
Reporter: David N'DIAYE
My pom have parent pom which is not in the {{repo1.maven.org}}. And i can't
initialize it because maven task ant {{pom}} doesn't find parent pom.
I need to have possibility to specify the remote repository like in the
dependencies task
{code:xml}
artifact:pom id=pom file=${pom.location} settingsFile=${settings.file}
*remoteRepository refid=remote.repository /*
localRepository location=${local.repository} /
/artifact:pom
{code}
I have the same problem with the {{install-provider}} to download my
dependencies. I can't specify the remote repository, so i can't download all
dependencies which is not in {{repo1.maven.org}}.
{code:xml}
artifact:install-provider artifactId=wagon-ftp version=1.0-beta-2
*remoteRepository refid=remote.repository /*
/artifact:install-provider
{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] Commented: (MANTTASKS-68) artifact:depencies doesnt work with Snapshot
[
http://jira.codehaus.org/browse/MANTTASKS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94763
]
David N'DIAYE commented on MANTTASKS-68:
I confirm, MANTTASKS-18 solve my problem.
I vote for your issue, and i close this jira
thanks a lot
artifact:depencies doesnt work with Snapshot
Key: MANTTASKS-68
URL: http://jira.codehaus.org/browse/MANTTASKS-68
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Affects Versions: 2.0.6
Reporter: David N'DIAYE
Attachments: testDependencySnapshots.zip
-- I have a repository with snapshot
-- I create a pom with a dependency to snapshot artifact
{code:xml}
dependencies
dependency
groupIdcommons-io/groupId
artifactIdcommons-io/artifactId
version1.3-SNAPSHOT/version
/dependency
/dependencies
{code}
-- In ant, I obtain dependencies on my application
{code:xml}
artifact:dependencies filesetId=compile.dependency.fileset
useScope=compile verbose=true
pom refid=pom /
remoteRepository refid=repository /
localRepository location=./cache /
/artifact:dependencies
{code}
The {{compile.dependency.fileset}} *doesn't contains the snapshot artifact*
To test this bug, you can launch my ant test by : {color:red} *{{ant
test}}*{color}
--
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: (MANTTASKS-68) artifact:depencies doesnt work with Snapshot
[
http://jira.codehaus.org/browse/MANTTASKS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David N'DIAYE closed MANTTASKS-68.
--
Resolution: Fixed
Solve by patch MANTTASKS-18
artifact:depencies doesnt work with Snapshot
Key: MANTTASKS-68
URL: http://jira.codehaus.org/browse/MANTTASKS-68
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Affects Versions: 2.0.6
Reporter: David N'DIAYE
Attachments: testDependencySnapshots.zip
-- I have a repository with snapshot
-- I create a pom with a dependency to snapshot artifact
{code:xml}
dependencies
dependency
groupIdcommons-io/groupId
artifactIdcommons-io/artifactId
version1.3-SNAPSHOT/version
/dependency
/dependencies
{code}
-- In ant, I obtain dependencies on my application
{code:xml}
artifact:dependencies filesetId=compile.dependency.fileset
useScope=compile verbose=true
pom refid=pom /
remoteRepository refid=repository /
localRepository location=./cache /
/artifact:dependencies
{code}
The {{compile.dependency.fileset}} *doesn't contains the snapshot artifact*
To test this bug, you can launch my ant test by : {color:red} *{{ant
test}}*{color}
--
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: (MANTTASKS-68) artifact:depencies doesnt work with Snapshot
artifact:depencies doesnt work with Snapshot
Key: MANTTASKS-68
URL: http://jira.codehaus.org/browse/MANTTASKS-68
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Affects Versions: 2.0.6
Reporter: David N'DIAYE
Attachments: testDependencySnapshots.zip
-- I have a repository with snapshot
-- I create a pom with a dependency to snapshot artifact
{code:xml}
dependencies
dependency
groupIdcommons-io/groupId
artifactIdcommons-io/artifactId
version1.3-SNAPSHOT/version
/dependency
/dependencies
{code}
-- In ant, I obtain dependencies on my application
{code:xml}
artifact:dependencies filesetId=compile.dependency.fileset
useScope=compile verbose=true
pom refid=pom /
remoteRepository refid=repository /
localRepository location=./cache /
/artifact:dependencies
{code}
The {{compile.dependency.fileset}} *doesn't contains the snapshot artifact*
To test this bug, you can launch my ant test by : {color:red} *{{ant
test}}*{color}
--
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: (MANTTASKS-67) artifact:deploy - The name of deploying element in snapshot repository is wrong
[
http://jira.codehaus.org/browse/MANTTASKS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93993
]
David N'DIAYE commented on MANTTASKS-67:
I'm sorry, it is my first jira, and i'm newby with your formatting notation.
I can't modify my description, so i copy it in this comment with a good format :
-
-- The zip file contains test with Ant. To launch it : {color:red}*{{ant
test.}}*{color}
I try to deploy a snapshot artifact in repository
-- my pom.xml contains a version with the extension '-SNAPSHOT'
-- in my build file Ant i do this :
{code:xml}
artifact:deploy file=lib/${pom.artifactId}.jar
remoteRepository url=file:./repository /
pom refid=pom /
/artifact:deploy
{code}
In the repository the name of the artifact is
{code:xml}artifactId-version-SNAPSHOT.packaging !-- Wrong Format --
{code} instead of
{code:xml}artifactId-version-date.time-buildNumber-packaging{code}
Another problem, i try to upload *2 attachments* with my artifact ({{javadoc}}
and {{java-source}}), and the *buildNumber* in the {{maven-metadata.xml}}
increment by {color:red}*3*{color} instead of *1*
{code:xml}artifact:deploy file=lib/${pom.artifactId}.jar
remoteRepository url=file:./repository /
pom refid=pom /
attach file=./lib/${pom.artifactId}-src.jar type=java-source/
attach file=./lib/${pom.artifactId}-api.zip type=javadoc/
/artifact:deploy{code}
You can test it with : {color:red}*{{ant testWithAttach.}}*{color}
artifact:deploy - The name of deploying element in snapshot repository is
wrong
---
Key: MANTTASKS-67
URL: http://jira.codehaus.org/browse/MANTTASKS-67
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Affects Versions: 2.0.6
Reporter: David N'DIAYE
Attachments: testSnapshots.zip
The zip file contains test with Ant.
To launch it : ant test.
I try to deploy a snapshot artifact in repository
So, my pom.xml contains a version with the extension '-SNAPSHOT'
And in my build file Ant i do this :
artifact:deploy file=lib/${pom.artifactId}.jar
remoteRepository url=file:./repository /
pom refid=pom /
/artifact:deploy
In the repository the name of the artifact is
artifactId-version-SNAPSHOT.packaging instead of
artifactId-version-date.time-buildNumber-packaging
Another problem, i try to upload 2 attachments with my artifact (javadoc and
java-source), and the buildNumber in the meta-data.xml increment by 3 instead
of 1
artifact:deploy file=lib/${pom.artifactId}.jar
remoteRepository url=file:./repository /
pom refid=pom /
attach file=./lib/${pom.artifactId}-src.jar type=java-source/
attach file=./lib/${pom.artifactId}-api.zip type=javadoc/
/artifact:deploy
You can test it with : ant testWithAttach
--
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: (MANTTASKS-67) artifact:deploy - The name of deploying element in snapshot repository is wrong
[
http://jira.codehaus.org/browse/MANTTASKS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93994
]
David N'DIAYE commented on MANTTASKS-67:
I haven't see the MANTTASKS-23, and i create a copy of it.
But my case contains an Ant testCase, and i find another problem with
attachment.
artifact:deploy - The name of deploying element in snapshot repository is
wrong
---
Key: MANTTASKS-67
URL: http://jira.codehaus.org/browse/MANTTASKS-67
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Affects Versions: 2.0.6
Reporter: David N'DIAYE
Attachments: testSnapshots.zip
The zip file contains test with Ant.
To launch it : ant test.
I try to deploy a snapshot artifact in repository
So, my pom.xml contains a version with the extension '-SNAPSHOT'
And in my build file Ant i do this :
artifact:deploy file=lib/${pom.artifactId}.jar
remoteRepository url=file:./repository /
pom refid=pom /
/artifact:deploy
In the repository the name of the artifact is
artifactId-version-SNAPSHOT.packaging instead of
artifactId-version-date.time-buildNumber-packaging
Another problem, i try to upload 2 attachments with my artifact (javadoc and
java-source), and the buildNumber in the meta-data.xml increment by 3 instead
of 1
artifact:deploy file=lib/${pom.artifactId}.jar
remoteRepository url=file:./repository /
pom refid=pom /
attach file=./lib/${pom.artifactId}-src.jar type=java-source/
attach file=./lib/${pom.artifactId}-api.zip type=javadoc/
/artifact:deploy
You can test it with : ant testWithAttach
--
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: (MANTTASKS-67) artifact:deploy - The name of deploying element in snapshot repository is wrong
artifact:deploy - The name of deploying element in snapshot repository is wrong
---
Key: MANTTASKS-67
URL: http://jira.codehaus.org/browse/MANTTASKS-67
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Affects Versions: 2.0.6
Reporter: David N'DIAYE
Attachments: testSnapshots.zip
The zip file contains test with Ant.
To launch it : ant test.
I try to deploy a snapshot artifact in repository
So, my pom.xml contains a version with the extension '-SNAPSHOT'
And in my build file Ant i do this :
artifact:deploy file=lib/${pom.artifactId}.jar
remoteRepository url=file:./repository /
pom refid=pom /
/artifact:deploy
In the repository the name of the artifact is
artifactId-version-SNAPSHOT.packaging instead of
artifactId-version-date.time-buildNumber-packaging
Another problem, i try to upload 2 attachments with my artifact (javadoc and
java-source), and the buildNumber in the meta-data.xml increment by 3 instead
of 1
artifact:deploy file=lib/${pom.artifactId}.jar
remoteRepository url=file:./repository /
pom refid=pom /
attach file=./lib/${pom.artifactId}-src.jar type=java-source/
attach file=./lib/${pom.artifactId}-api.zip type=javadoc/
/artifact:deploy
You can test it with : ant testWithAttach
--
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
