[
http://jira.codehaus.org/browse/MANTTASKS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MANTTASKS-23:
-----------------------------------
Assignee: Herve Boutemy
Description:
I'm trying to deploy to maven remote repository jars produced by
ant. Those jars are in snapshot version.
Whole deployment process is going properly, but something is wrong with names
of deployed files.
When I'm deploying artifacts using normal 'maven deploy', "SNAPSHOT" in
the name is replaced by the current timestamp and the snapshot number (for
instance: "20060105.123437-3").
But when I'm deploying with antlib, the name isn't changed. "SNAPSHOT" is
still in the name. And when I deploy snapshot again, the old one is
replaced by the new one (which also different from behavior of normal 'mvn
deploy').
The metadata.xml also is generated incorrectly. Timestamp in snapshot tag is
missing:
<?xml version="1.0" encoding="UTF-8"?><metadata>
<groupId>foo</groupId>
<artifactId>foo-jar1</artifactId>
<version>1.0-SNAPSHOT</version>
<versioning>
<snapshot>
<buildNumber>4</buildNumber>
</snapshot>
<lastUpdated>20060209111228</lastUpdated>
</versioning>
</metadata>
Here's an fragment of my ant script:
<target name="maven-poms">
<artifact:pom id="pom.jar1-jar" file="maven/pom-jar1-jar.xml" />
<artifact:pom id="pom.jar2-jar" file="maven/pom-jar2-jar.xml" />
<artifact:pom id="pom.jar3-jar" file="maven/pom-jar3--jar.xml" />
</target>
<target name="maven-install-local"
depends="maven-poms,generate-jars">
<artifact:install file="${build.dir}/jar1.jar">
<pom refid="pom.jar1-jar"/>
</artifact:install>
<artifact:install file="${build.dir}/jar2.jar">
<pom refid="pom.jar2-jar"/>
</artifact:install>
<artifact:install file="${build.dir}/jar3.jar">
<pom refid="pom.jar3-jar"/>
</artifact:install>
</target>
<target name="maven-deploy-remote" depends="maven-install-local">
<artifact:install-provider artifactId="wagon-ssh" version="1.0-alpha-5"/>
<artifact:deploy file="${build.dir}/jar1.jar">
<pom refid="pom.jar1-jar"/>
</artifact:deploy>
<artifact:deploy file="${build.dir}/jar2.jar">
<pom refid="pom.jar2-jar"/>
</artifact:deploy>
<artifact:deploy file="${build.dir}/jar3.jar">
<pom refid="pom.jar3-jar"/>
</artifact:deploy>
</target>
The artifacts poms are in separate files which contain only artifactId,
groupId,
version, dependencies and remote repository url.
I also tried to deploy using 'mvn -f pom-file.xml deploy' to check if my
repository
url is specified correctly. And it works. Jar is deployed to remote repository
with
correct version.
was:
I'm trying to deploy to maven remote repository jars produced by
ant. Those jars are in snapshot version.
Whole deployment process is going properly, but something is wrong with names
of deployed files.
When I'm deploying artifacts using normal 'maven deploy', "SNAPSHOT" in
the name is replaced by the current timestamp and the snapshot number (for
instance: "20060105.123437-3").
But when I'm deploying with antlib, the name isn't changed. "SNAPSHOT" is
still in the name. And when I deploy snapshot again, the old one is
replaced by the new one (which also different from behavior of normal 'mvn
deploy').
The metadata.xml also is generated incorrectly. Timestamp in snapshot tag is
missing:
<?xml version="1.0" encoding="UTF-8"?><metadata>
<groupId>foo</groupId>
<artifactId>foo-jar1</artifactId>
<version>1.0-SNAPSHOT</version>
<versioning>
<snapshot>
<buildNumber>4</buildNumber>
</snapshot>
<lastUpdated>20060209111228</lastUpdated>
</versioning>
</metadata>
Here's an fragment of my ant script:
<target name="maven-poms">
<artifact:pom id="pom.jar1-jar" file="maven/pom-jar1-jar.xml" />
<artifact:pom id="pom.jar2-jar" file="maven/pom-jar2-jar.xml" />
<artifact:pom id="pom.jar3-jar" file="maven/pom-jar3--jar.xml" />
</target>
<target name="maven-install-local"
depends="maven-poms,generate-jars">
<artifact:install file="${build.dir}/jar1.jar">
<pom refid="pom.jar1-jar"/>
</artifact:install>
<artifact:install file="${build.dir}/jar2.jar">
<pom refid="pom.jar2-jar"/>
</artifact:install>
<artifact:install file="${build.dir}/jar3.jar">
<pom refid="pom.jar3-jar"/>
</artifact:install>
</target>
<target name="maven-deploy-remote" depends="maven-install-local">
<artifact:install-provider artifactId="wagon-ssh" version="1.0-alpha-5"/>
<artifact:deploy file="${build.dir}/jar1.jar">
<pom refid="pom.jar1-jar"/>
</artifact:deploy>
<artifact:deploy file="${build.dir}/jar2.jar">
<pom refid="pom.jar2-jar"/>
</artifact:deploy>
<artifact:deploy file="${build.dir}/jar3.jar">
<pom refid="pom.jar3-jar"/>
</artifact:deploy>
</target>
The artifacts poms are in separate files which contain only artifactId,
groupId,
version, dependencies and remote repository url.
I also tried to deploy using 'mvn -f pom-file.xml deploy' to check if my
repository
url is specified correctly. And it works. Jar is deployed to remote repository
with
correct version.
Remaining Estimate: 0 minutes
Original Estimate: 0 minutes
> antlib:deploy doesn't set correct snapshot version
> --------------------------------------------------
>
> Key: MANTTASKS-23
> URL: http://jira.codehaus.org/browse/MANTTASKS-23
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: deploy task
> Affects Versions: 2.0.4, 2.0.6, 2.0.7
> Environment: win xp, mvn 2.0.2, ant 1.6.5
> Reporter: Michal Stochmialek
> Assignee: Herve Boutemy
> Fix For: 2.0.8
>
> Attachments: MANTTASKS-23.diff, MANTTASKS-23_site.diff,
> maven-artifact-ant-MNG-2060.patch
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> I'm trying to deploy to maven remote repository jars produced by
> ant. Those jars are in snapshot version.
> Whole deployment process is going properly, but something is wrong with names
> of deployed files.
> When I'm deploying artifacts using normal 'maven deploy', "SNAPSHOT" in
> the name is replaced by the current timestamp and the snapshot number (for
> instance: "20060105.123437-3").
> But when I'm deploying with antlib, the name isn't changed. "SNAPSHOT" is
> still in the name. And when I deploy snapshot again, the old one is
> replaced by the new one (which also different from behavior of normal 'mvn
> deploy').
> The metadata.xml also is generated incorrectly. Timestamp in snapshot tag is
> missing:
> <?xml version="1.0" encoding="UTF-8"?><metadata>
> <groupId>foo</groupId>
> <artifactId>foo-jar1</artifactId>
> <version>1.0-SNAPSHOT</version>
> <versioning>
> <snapshot>
> <buildNumber>4</buildNumber>
> </snapshot>
> <lastUpdated>20060209111228</lastUpdated>
> </versioning>
> </metadata>
> Here's an fragment of my ant script:
> <target name="maven-poms">
> <artifact:pom id="pom.jar1-jar" file="maven/pom-jar1-jar.xml" />
> <artifact:pom id="pom.jar2-jar" file="maven/pom-jar2-jar.xml" />
> <artifact:pom id="pom.jar3-jar" file="maven/pom-jar3--jar.xml" />
> </target>
> <target name="maven-install-local"
> depends="maven-poms,generate-jars">
> <artifact:install file="${build.dir}/jar1.jar">
> <pom refid="pom.jar1-jar"/>
> </artifact:install>
> <artifact:install file="${build.dir}/jar2.jar">
> <pom refid="pom.jar2-jar"/>
> </artifact:install>
> <artifact:install file="${build.dir}/jar3.jar">
> <pom refid="pom.jar3-jar"/>
> </artifact:install>
> </target>
> <target name="maven-deploy-remote" depends="maven-install-local">
> <artifact:install-provider artifactId="wagon-ssh" version="1.0-alpha-5"/>
>
> <artifact:deploy file="${build.dir}/jar1.jar">
> <pom refid="pom.jar1-jar"/>
> </artifact:deploy>
> <artifact:deploy file="${build.dir}/jar2.jar">
> <pom refid="pom.jar2-jar"/>
> </artifact:deploy>
> <artifact:deploy file="${build.dir}/jar3.jar">
> <pom refid="pom.jar3-jar"/>
> </artifact:deploy>
> </target>
> The artifacts poms are in separate files which contain only artifactId,
> groupId,
> version, dependencies and remote repository url.
> I also tried to deploy using 'mvn -f pom-file.xml deploy' to check if my
> repository
> url is specified correctly. And it works. Jar is deployed to remote
> repository with
> correct 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
