You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Paul McMahan <pa...@gmail.com> on 2007/03/27 17:04:31 UTC
Re: Tomcat m2 repo?
A few months ago I opened a tomcat issue requesting them to publish
the tomcat jars to a maven repo.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41093
Yesterday they marked the issue as resolved since the tomcat jars are
now available at http://tomcat.apache.org/dev/dist/m2-repository, but
commented that they would publish to central if there is a way to work
around a problem with PGP signatures:
> Doesn't seem like I can publish to the central repo
> because it requires PGP signatures and maven
> doesn't let you do that with single JAR if you're not
> building with Maven.
>
> If you have a way to get the PGP info in there in
> the way we are doing it now, let us know and
> open a new bug.
If anyone knows of a way to sign single JARs not built with maven then
please enlighten us or just go ahead open a new tomcat bug with the
details. This may be the only remaining impediment towards making the
tomcat jars available on central.
Best wishes,
Paul
On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
> Okay, hopefully they will get the kinks out soon ;-)
>
> --jason
>
>
> On Feb 13, 2007, at 4:39 PM, Paul McMahan wrote:
>
> > Tomcat currently builds with ant and then manually publish their jars
> > to a repo at tomcat.apache.org. See
> > http://www.nabble.com/Tomcat-Jars---Maven2-repo-
> > tf3023226.html#a8397986
> > They have only just started to make publishing to an m2 repo part of
> > their release process, and IIUC they want to work the kinks out of
> > their scripts before pointing them at central.
> >
> > Best wishes,
> > Paul
> >
> > On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
> >> Why do we need this repo:
> >>
> >> http://tomcat.apache.org/dev/dist/m2-repository
> >>
> >> Is Tomcat not publishing to central? If not... anyone know why?
> >>
> >> --jason
> >>
>
>
Re: Tomcat m2 repo?
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Jason Dillon wrote:
> Mocking me? Ha... I prolly deserve it a little :-P
>
> But I'm here if you need more help.
sounds good
Filip
>
> --jason
>
>
> On Mar 30, 2007, at 4:58 PM, Filip Hanik - Dev Lists wrote:
>
>> eeeh, and you were asking why we havent got around to this?
>> "lack of expertise" if I remember correctly :)
>>
>> Just messing with you Jason....
>>
>> Filip
>>
>>
>> Jason Dillon wrote:
>>> Until Jason gets to releasing the updated tasks you will need to
>>> build a few bits by hand to use the new antlib attach stuff.
>>>
>>> First build Maven 2.0.6 from its tag:
>>>
>>> http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.6/
>>>
>>> And then build the updated ant tasks from this feature branch:
>>>
>>>
>>> http://svn.apache.org/repos/asf/maven/sandbox/trunk/ant-tasks/install-deploy-attached/
>>>
>>>
>>> Both should build with no problems with Maven 2.0.5.
>>>
>>> Then you should have <artifact:install> and <artifact:deploy> tasks
>>> which support a nested <attach file="" type=""/> elements as
>>> documented in the JIRA issue:
>>>
>>> http://jira.codehaus.org/browse/MANTTASKS-42
>>>
>>> Let me know if you run into any issues and I will do what I can to
>>> help you resolve them.
>>>
>>> Cheers,
>>>
>>> --jason
>>>
>>>
>>> On Mar 30, 2007, at 1:26 PM, Filip Hanik - Dev Lists wrote:
>>>
>>>> I'll give the antlibs another shot
>>>>
>>>> Filip
>>>>
>>>> Jason Dillon wrote:
>>>>> FYI the issue + patch to the tasks is here:
>>>>>
>>>>> http://jira.codehaus.org/browse/MANTTASKS-42
>>>>>
>>>>> --jason
>>>>>
>>>>>
>>>>> On Mar 29, 2007, at 6:39 AM, Filip Hanik - Dev Lists wrote:
>>>>>
>>>>>> Jason Dillon wrote:
>>>>>>> On Mar 27, 2007, at 4:50 PM, Filip Hanik - Dev Lists wrote:
>>>>>>>>> I don't expect that Tomcat will switch to m2, though if they
>>>>>>>>> are gonna be publishing m2 repos they should use the m2 antlib
>>>>>>>>> for that. But, looks like the m2 antlib is not up to snuff
>>>>>>>>> wrt the new? apache requirements to publish .asc files for
>>>>>>>>> releases. I think the antlib tasks probably need to be
>>>>>>>>> updated to allow extra files to be attached when
>>>>>>>>> install/deploying and then ant folks should be sorted... well,
>>>>>>>>> that and if they implement a task or macro to sign stuff.
>>>>>>>> we're note even using the antlibs, they were not really working
>>>>>>>> out. It was easier to just exec the mvn script directly. If
>>>>>>>> Maven has the command line option to do what we want, then we
>>>>>>>> can do it.
>>>>>>>
>>>>>>> Just curious, what wasn't working out with the antlibs? They
>>>>>>> should prolly be fixed if they are not usable by ant projects.
>>>>>>>
>>>>>>>
>>>>>>>> So if you show me the "$MAVEN_HOME/bin/mvn" command to publish
>>>>>>>> a single JAR(with a POM) and being able to make sure the
>>>>>>>> signature goes with it, then we are fine.
>>>>>>>> GPG signing is a no brainer, we can do that any day.
>>>>>>>
>>>>>>> Hrm... I'm not sure there exists such a command at the moment,
>>>>>>> though its probably easy enough to craft a simple goal to
>>>>>>> implement what you need.
>>>>>> yeah, I might just implement this in ANT all together, and skip
>>>>>> maven, if it is a simple SCP copy.
>>>>>>>
>>>>>>> The reason it doesn't work asis, is that the gpg .asc stuff is
>>>>>>> attached to the current projects artifact and the install/deploy
>>>>>>> will handle the primary artifact and then any attached artifacts
>>>>>>> separately. The install-file/deploy-file goals don't have a
>>>>>>> project to work on so there is nothing to attach to.
>>>>>>>
>>>>>>> I suppose that either install-file/deploy-file need to take an
>>>>>>> additional csv list of other files to "attach" or perhaps simply
>>>>>>> craft a pom.xml which uses build-helper:attach-artifact (
>>>>>>> http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
>>>>>>> ) and dance around mvn a little to make `mvn deploy` work.
>>>>>>>
>>>>>>> But, it would really be better IMO, to use the <deploy> task and
>>>>>>> update the task to have a nested set of <attached-file> elements
>>>>>>> which can be used to effectively behave the same as mvn would
>>>>>>> normally by deploying the primary artifact, and then any
>>>>>>> attached artifacts. Thats *much* less of a hack.
>>>>>>>
>>>>>>> Can you tell me why the antlib tasks aren't working for you?
>>>>>> there were a few things
>>>>>> 1. documentation or my inability to work with it
>>>>>> 2. learning curve, I'm trying to do something really simple
>>>>>> 3. SCP with maven on windows simply didn't work, turns out that
>>>>>> it still doesn't work when using the command line arguments, so I
>>>>>> am still running from linux.
>>>>>>
>>>>>> since all I wanna do is SCP a .jar .pom .md5 and .asc, why does
>>>>>> this have to be so complicated :)
>>>>>> if I can reverse engineer what it is Maven is doing when
>>>>>> publishing a file to a repo, it will be easier for me to
>>>>>> implement it in pure ant.
>>>>>>
>>>>>> Filip
>>>>>>>
>>>>>>> --jason
>>>>>>>
>>>>>>>
>>>>>>> --No virus found in this incoming message.
>>>>>>> Checked by AVG Free Edition.
>>>>>>> Version: 7.5.446 / Virus Database: 268.18.18/734 - Release Date:
>>>>>>> 3/26/2007 2:31 PM
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --No virus found in this incoming message.
>>>>> Checked by AVG Free Edition.
>>>>> Version: 7.5.446 / Virus Database: 268.18.20/737 - Release Date:
>>>>> 3/28/2007 4:23 PM
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --No virus found in this incoming message.
>>> Checked by AVG Free Edition.
>>> Version: 7.5.446 / Virus Database: 268.18.22/739 - Release Date:
>>> 3/29/2007 1:36 PM
>>>
>>>
>>
>
>
>
> --No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.22/739 - Release Date:
> 3/29/2007 1:36 PM
>
>
Re: Tomcat m2 repo?
Posted by Jason Dillon <ja...@planet57.com>.
Mocking me? Ha... I prolly deserve it a little :-P
But I'm here if you need more help.
--jason
On Mar 30, 2007, at 4:58 PM, Filip Hanik - Dev Lists wrote:
> eeeh, and you were asking why we havent got around to this?
> "lack of expertise" if I remember correctly :)
>
> Just messing with you Jason....
>
> Filip
>
>
> Jason Dillon wrote:
>> Until Jason gets to releasing the updated tasks you will need to
>> build a few bits by hand to use the new antlib attach stuff.
>>
>> First build Maven 2.0.6 from its tag:
>>
>> http://svn.apache.org/repos/asf/maven/components/tags/
>> maven-2.0.6/
>>
>> And then build the updated ant tasks from this feature branch:
>>
>> http://svn.apache.org/repos/asf/maven/sandbox/trunk/ant-tasks/
>> install-deploy-attached/
>>
>> Both should build with no problems with Maven 2.0.5.
>>
>> Then you should have <artifact:install> and <artifact:deploy>
>> tasks which support a nested <attach file="" type=""/> elements as
>> documented in the JIRA issue:
>>
>> http://jira.codehaus.org/browse/MANTTASKS-42
>>
>> Let me know if you run into any issues and I will do what I can to
>> help you resolve them.
>>
>> Cheers,
>>
>> --jason
>>
>>
>> On Mar 30, 2007, at 1:26 PM, Filip Hanik - Dev Lists wrote:
>>
>>> I'll give the antlibs another shot
>>>
>>> Filip
>>>
>>> Jason Dillon wrote:
>>>> FYI the issue + patch to the tasks is here:
>>>>
>>>> http://jira.codehaus.org/browse/MANTTASKS-42
>>>>
>>>> --jason
>>>>
>>>>
>>>> On Mar 29, 2007, at 6:39 AM, Filip Hanik - Dev Lists wrote:
>>>>
>>>>> Jason Dillon wrote:
>>>>>> On Mar 27, 2007, at 4:50 PM, Filip Hanik - Dev Lists wrote:
>>>>>>>> I don't expect that Tomcat will switch to m2, though if they
>>>>>>>> are gonna be publishing m2 repos they should use the m2
>>>>>>>> antlib for that. But, looks like the m2 antlib is not up to
>>>>>>>> snuff wrt the new? apache requirements to publish .asc files
>>>>>>>> for releases. I think the antlib tasks probably need to be
>>>>>>>> updated to allow extra files to be attached when install/
>>>>>>>> deploying and then ant folks should be sorted... well, that
>>>>>>>> and if they implement a task or macro to sign stuff.
>>>>>>> we're note even using the antlibs, they were not really
>>>>>>> working out. It was easier to just exec the mvn script
>>>>>>> directly. If Maven has the command line option to do what we
>>>>>>> want, then we can do it.
>>>>>>
>>>>>> Just curious, what wasn't working out with the antlibs? They
>>>>>> should prolly be fixed if they are not usable by ant projects.
>>>>>>
>>>>>>
>>>>>>> So if you show me the "$MAVEN_HOME/bin/mvn" command to
>>>>>>> publish a single JAR(with a POM) and being able to make sure
>>>>>>> the signature goes with it, then we are fine.
>>>>>>> GPG signing is a no brainer, we can do that any day.
>>>>>>
>>>>>> Hrm... I'm not sure there exists such a command at the moment,
>>>>>> though its probably easy enough to craft a simple goal to
>>>>>> implement what you need.
>>>>> yeah, I might just implement this in ANT all together, and skip
>>>>> maven, if it is a simple SCP copy.
>>>>>>
>>>>>> The reason it doesn't work asis, is that the gpg .asc stuff is
>>>>>> attached to the current projects artifact and the install/
>>>>>> deploy will handle the primary artifact and then any attached
>>>>>> artifacts separately. The install-file/deploy-file goals
>>>>>> don't have a project to work on so there is nothing to attach to.
>>>>>>
>>>>>> I suppose that either install-file/deploy-file need to take an
>>>>>> additional csv list of other files to "attach" or perhaps
>>>>>> simply craft a pom.xml which uses build-helper:attach-artifact
>>>>>> ( http://mojo.codehaus.org/build-helper-maven-plugin/attach-
>>>>>> artifact-mojo.html ) and dance around mvn a little to make
>>>>>> `mvn deploy` work.
>>>>>>
>>>>>> But, it would really be better IMO, to use the <deploy> task
>>>>>> and update the task to have a nested set of <attached-file>
>>>>>> elements which can be used to effectively behave the same as
>>>>>> mvn would normally by deploying the primary artifact, and then
>>>>>> any attached artifacts. Thats *much* less of a hack.
>>>>>>
>>>>>> Can you tell me why the antlib tasks aren't working for you?
>>>>> there were a few things
>>>>> 1. documentation or my inability to work with it
>>>>> 2. learning curve, I'm trying to do something really simple
>>>>> 3. SCP with maven on windows simply didn't work, turns out that
>>>>> it still doesn't work when using the command line arguments, so
>>>>> I am still running from linux.
>>>>>
>>>>> since all I wanna do is SCP a .jar .pom .md5 and .asc, why does
>>>>> this have to be so complicated :)
>>>>> if I can reverse engineer what it is Maven is doing when
>>>>> publishing a file to a repo, it will be easier for me to
>>>>> implement it in pure ant.
>>>>>
>>>>> Filip
>>>>>>
>>>>>> --jason
>>>>>>
>>>>>>
>>>>>> --No virus found in this incoming message.
>>>>>> Checked by AVG Free Edition.
>>>>>> Version: 7.5.446 / Virus Database: 268.18.18/734 - Release
>>>>>> Date: 3/26/2007 2:31 PM
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --No virus found in this incoming message.
>>>> Checked by AVG Free Edition.
>>>> Version: 7.5.446 / Virus Database: 268.18.20/737 - Release Date:
>>>> 3/28/2007 4:23 PM
>>>>
>>>>
>>>
>>
>>
>>
>> --No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.5.446 / Virus Database: 268.18.22/739 - Release Date:
>> 3/29/2007 1:36 PM
>>
>>
>
Re: Tomcat m2 repo?
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
eeeh, and you were asking why we havent got around to this?
"lack of expertise" if I remember correctly :)
Just messing with you Jason....
Filip
Jason Dillon wrote:
> Until Jason gets to releasing the updated tasks you will need to build
> a few bits by hand to use the new antlib attach stuff.
>
> First build Maven 2.0.6 from its tag:
>
> http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.6/
>
> And then build the updated ant tasks from this feature branch:
>
>
> http://svn.apache.org/repos/asf/maven/sandbox/trunk/ant-tasks/install-deploy-attached/
>
>
> Both should build with no problems with Maven 2.0.5.
>
> Then you should have <artifact:install> and <artifact:deploy> tasks
> which support a nested <attach file="" type=""/> elements as
> documented in the JIRA issue:
>
> http://jira.codehaus.org/browse/MANTTASKS-42
>
> Let me know if you run into any issues and I will do what I can to
> help you resolve them.
>
> Cheers,
>
> --jason
>
>
> On Mar 30, 2007, at 1:26 PM, Filip Hanik - Dev Lists wrote:
>
>> I'll give the antlibs another shot
>>
>> Filip
>>
>> Jason Dillon wrote:
>>> FYI the issue + patch to the tasks is here:
>>>
>>> http://jira.codehaus.org/browse/MANTTASKS-42
>>>
>>> --jason
>>>
>>>
>>> On Mar 29, 2007, at 6:39 AM, Filip Hanik - Dev Lists wrote:
>>>
>>>> Jason Dillon wrote:
>>>>> On Mar 27, 2007, at 4:50 PM, Filip Hanik - Dev Lists wrote:
>>>>>>> I don't expect that Tomcat will switch to m2, though if they are
>>>>>>> gonna be publishing m2 repos they should use the m2 antlib for
>>>>>>> that. But, looks like the m2 antlib is not up to snuff wrt the
>>>>>>> new? apache requirements to publish .asc files for releases. I
>>>>>>> think the antlib tasks probably need to be updated to allow
>>>>>>> extra files to be attached when install/deploying and then ant
>>>>>>> folks should be sorted... well, that and if they implement a
>>>>>>> task or macro to sign stuff.
>>>>>> we're note even using the antlibs, they were not really working
>>>>>> out. It was easier to just exec the mvn script directly. If Maven
>>>>>> has the command line option to do what we want, then we can do it.
>>>>>
>>>>> Just curious, what wasn't working out with the antlibs? They
>>>>> should prolly be fixed if they are not usable by ant projects.
>>>>>
>>>>>
>>>>>> So if you show me the "$MAVEN_HOME/bin/mvn" command to publish a
>>>>>> single JAR(with a POM) and being able to make sure the signature
>>>>>> goes with it, then we are fine.
>>>>>> GPG signing is a no brainer, we can do that any day.
>>>>>
>>>>> Hrm... I'm not sure there exists such a command at the moment,
>>>>> though its probably easy enough to craft a simple goal to
>>>>> implement what you need.
>>>> yeah, I might just implement this in ANT all together, and skip
>>>> maven, if it is a simple SCP copy.
>>>>>
>>>>> The reason it doesn't work asis, is that the gpg .asc stuff is
>>>>> attached to the current projects artifact and the install/deploy
>>>>> will handle the primary artifact and then any attached artifacts
>>>>> separately. The install-file/deploy-file goals don't have a
>>>>> project to work on so there is nothing to attach to.
>>>>>
>>>>> I suppose that either install-file/deploy-file need to take an
>>>>> additional csv list of other files to "attach" or perhaps simply
>>>>> craft a pom.xml which uses build-helper:attach-artifact (
>>>>> http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
>>>>> ) and dance around mvn a little to make `mvn deploy` work.
>>>>>
>>>>> But, it would really be better IMO, to use the <deploy> task and
>>>>> update the task to have a nested set of <attached-file> elements
>>>>> which can be used to effectively behave the same as mvn would
>>>>> normally by deploying the primary artifact, and then any attached
>>>>> artifacts. Thats *much* less of a hack.
>>>>>
>>>>> Can you tell me why the antlib tasks aren't working for you?
>>>> there were a few things
>>>> 1. documentation or my inability to work with it
>>>> 2. learning curve, I'm trying to do something really simple
>>>> 3. SCP with maven on windows simply didn't work, turns out that it
>>>> still doesn't work when using the command line arguments, so I am
>>>> still running from linux.
>>>>
>>>> since all I wanna do is SCP a .jar .pom .md5 and .asc, why does
>>>> this have to be so complicated :)
>>>> if I can reverse engineer what it is Maven is doing when publishing
>>>> a file to a repo, it will be easier for me to implement it in pure
>>>> ant.
>>>>
>>>> Filip
>>>>>
>>>>> --jason
>>>>>
>>>>>
>>>>> --No virus found in this incoming message.
>>>>> Checked by AVG Free Edition.
>>>>> Version: 7.5.446 / Virus Database: 268.18.18/734 - Release Date:
>>>>> 3/26/2007 2:31 PM
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --No virus found in this incoming message.
>>> Checked by AVG Free Edition.
>>> Version: 7.5.446 / Virus Database: 268.18.20/737 - Release Date:
>>> 3/28/2007 4:23 PM
>>>
>>>
>>
>
>
>
> --No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.22/739 - Release Date:
> 3/29/2007 1:36 PM
>
>
Re: Tomcat m2 repo?
Posted by Jason Dillon <ja...@planet57.com>.
Until Jason gets to releasing the updated tasks you will need to
build a few bits by hand to use the new antlib attach stuff.
First build Maven 2.0.6 from its tag:
http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.6/
And then build the updated ant tasks from this feature branch:
http://svn.apache.org/repos/asf/maven/sandbox/trunk/ant-tasks/
install-deploy-attached/
Both should build with no problems with Maven 2.0.5.
Then you should have <artifact:install> and <artifact:deploy> tasks
which support a nested <attach file="" type=""/> elements as
documented in the JIRA issue:
http://jira.codehaus.org/browse/MANTTASKS-42
Let me know if you run into any issues and I will do what I can to
help you resolve them.
Cheers,
--jason
On Mar 30, 2007, at 1:26 PM, Filip Hanik - Dev Lists wrote:
> I'll give the antlibs another shot
>
> Filip
>
> Jason Dillon wrote:
>> FYI the issue + patch to the tasks is here:
>>
>> http://jira.codehaus.org/browse/MANTTASKS-42
>>
>> --jason
>>
>>
>> On Mar 29, 2007, at 6:39 AM, Filip Hanik - Dev Lists wrote:
>>
>>> Jason Dillon wrote:
>>>> On Mar 27, 2007, at 4:50 PM, Filip Hanik - Dev Lists wrote:
>>>>>> I don't expect that Tomcat will switch to m2, though if they
>>>>>> are gonna be publishing m2 repos they should use the m2 antlib
>>>>>> for that. But, looks like the m2 antlib is not up to snuff
>>>>>> wrt the new? apache requirements to publish .asc files for
>>>>>> releases. I think the antlib tasks probably need to be
>>>>>> updated to allow extra files to be attached when install/
>>>>>> deploying and then ant folks should be sorted... well, that
>>>>>> and if they implement a task or macro to sign stuff.
>>>>> we're note even using the antlibs, they were not really working
>>>>> out. It was easier to just exec the mvn script directly. If
>>>>> Maven has the command line option to do what we want, then we
>>>>> can do it.
>>>>
>>>> Just curious, what wasn't working out with the antlibs? They
>>>> should prolly be fixed if they are not usable by ant projects.
>>>>
>>>>
>>>>> So if you show me the "$MAVEN_HOME/bin/mvn" command to publish
>>>>> a single JAR(with a POM) and being able to make sure the
>>>>> signature goes with it, then we are fine.
>>>>> GPG signing is a no brainer, we can do that any day.
>>>>
>>>> Hrm... I'm not sure there exists such a command at the moment,
>>>> though its probably easy enough to craft a simple goal to
>>>> implement what you need.
>>> yeah, I might just implement this in ANT all together, and skip
>>> maven, if it is a simple SCP copy.
>>>>
>>>> The reason it doesn't work asis, is that the gpg .asc stuff is
>>>> attached to the current projects artifact and the install/deploy
>>>> will handle the primary artifact and then any attached artifacts
>>>> separately. The install-file/deploy-file goals don't have a
>>>> project to work on so there is nothing to attach to.
>>>>
>>>> I suppose that either install-file/deploy-file need to take an
>>>> additional csv list of other files to "attach" or perhaps simply
>>>> craft a pom.xml which uses build-helper:attach-artifact ( http://
>>>> mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-
>>>> mojo.html ) and dance around mvn a little to make `mvn deploy`
>>>> work.
>>>>
>>>> But, it would really be better IMO, to use the <deploy> task and
>>>> update the task to have a nested set of <attached-file> elements
>>>> which can be used to effectively behave the same as mvn would
>>>> normally by deploying the primary artifact, and then any
>>>> attached artifacts. Thats *much* less of a hack.
>>>>
>>>> Can you tell me why the antlib tasks aren't working for you?
>>> there were a few things
>>> 1. documentation or my inability to work with it
>>> 2. learning curve, I'm trying to do something really simple
>>> 3. SCP with maven on windows simply didn't work, turns out that
>>> it still doesn't work when using the command line arguments, so I
>>> am still running from linux.
>>>
>>> since all I wanna do is SCP a .jar .pom .md5 and .asc, why does
>>> this have to be so complicated :)
>>> if I can reverse engineer what it is Maven is doing when
>>> publishing a file to a repo, it will be easier for me to
>>> implement it in pure ant.
>>>
>>> Filip
>>>>
>>>> --jason
>>>>
>>>>
>>>> --No virus found in this incoming message.
>>>> Checked by AVG Free Edition.
>>>> Version: 7.5.446 / Virus Database: 268.18.18/734 - Release Date:
>>>> 3/26/2007 2:31 PM
>>>>
>>>>
>>>
>>
>>
>>
>> --No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.5.446 / Virus Database: 268.18.20/737 - Release Date:
>> 3/28/2007 4:23 PM
>>
>>
>
Re: Tomcat m2 repo?
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
I'll give the antlibs another shot
Filip
Jason Dillon wrote:
> FYI the issue + patch to the tasks is here:
>
> http://jira.codehaus.org/browse/MANTTASKS-42
>
> --jason
>
>
> On Mar 29, 2007, at 6:39 AM, Filip Hanik - Dev Lists wrote:
>
>> Jason Dillon wrote:
>>> On Mar 27, 2007, at 4:50 PM, Filip Hanik - Dev Lists wrote:
>>>>> I don't expect that Tomcat will switch to m2, though if they are
>>>>> gonna be publishing m2 repos they should use the m2 antlib for
>>>>> that. But, looks like the m2 antlib is not up to snuff wrt the
>>>>> new? apache requirements to publish .asc files for releases. I
>>>>> think the antlib tasks probably need to be updated to allow extra
>>>>> files to be attached when install/deploying and then ant folks
>>>>> should be sorted... well, that and if they implement a task or
>>>>> macro to sign stuff.
>>>> we're note even using the antlibs, they were not really working
>>>> out. It was easier to just exec the mvn script directly. If Maven
>>>> has the command line option to do what we want, then we can do it.
>>>
>>> Just curious, what wasn't working out with the antlibs? They should
>>> prolly be fixed if they are not usable by ant projects.
>>>
>>>
>>>> So if you show me the "$MAVEN_HOME/bin/mvn" command to publish a
>>>> single JAR(with a POM) and being able to make sure the signature
>>>> goes with it, then we are fine.
>>>> GPG signing is a no brainer, we can do that any day.
>>>
>>> Hrm... I'm not sure there exists such a command at the moment,
>>> though its probably easy enough to craft a simple goal to implement
>>> what you need.
>> yeah, I might just implement this in ANT all together, and skip
>> maven, if it is a simple SCP copy.
>>>
>>> The reason it doesn't work asis, is that the gpg .asc stuff is
>>> attached to the current projects artifact and the install/deploy
>>> will handle the primary artifact and then any attached artifacts
>>> separately. The install-file/deploy-file goals don't have a project
>>> to work on so there is nothing to attach to.
>>>
>>> I suppose that either install-file/deploy-file need to take an
>>> additional csv list of other files to "attach" or perhaps simply
>>> craft a pom.xml which uses build-helper:attach-artifact (
>>> http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
>>> ) and dance around mvn a little to make `mvn deploy` work.
>>>
>>> But, it would really be better IMO, to use the <deploy> task and
>>> update the task to have a nested set of <attached-file> elements
>>> which can be used to effectively behave the same as mvn would
>>> normally by deploying the primary artifact, and then any attached
>>> artifacts. Thats *much* less of a hack.
>>>
>>> Can you tell me why the antlib tasks aren't working for you?
>> there were a few things
>> 1. documentation or my inability to work with it
>> 2. learning curve, I'm trying to do something really simple
>> 3. SCP with maven on windows simply didn't work, turns out that it
>> still doesn't work when using the command line arguments, so I am
>> still running from linux.
>>
>> since all I wanna do is SCP a .jar .pom .md5 and .asc, why does this
>> have to be so complicated :)
>> if I can reverse engineer what it is Maven is doing when publishing a
>> file to a repo, it will be easier for me to implement it in pure ant.
>>
>> Filip
>>>
>>> --jason
>>>
>>>
>>> --No virus found in this incoming message.
>>> Checked by AVG Free Edition.
>>> Version: 7.5.446 / Virus Database: 268.18.18/734 - Release Date:
>>> 3/26/2007 2:31 PM
>>>
>>>
>>
>
>
>
> --No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.20/737 - Release Date:
> 3/28/2007 4:23 PM
>
>
Re: Tomcat m2 repo?
Posted by Jason Dillon <ja...@planet57.com>.
FYI the issue + patch to the tasks is here:
http://jira.codehaus.org/browse/MANTTASKS-42
--jason
On Mar 29, 2007, at 6:39 AM, Filip Hanik - Dev Lists wrote:
> Jason Dillon wrote:
>> On Mar 27, 2007, at 4:50 PM, Filip Hanik - Dev Lists wrote:
>>>> I don't expect that Tomcat will switch to m2, though if they are
>>>> gonna be publishing m2 repos they should use the m2 antlib for
>>>> that. But, looks like the m2 antlib is not up to snuff wrt the
>>>> new? apache requirements to publish .asc files for releases. I
>>>> think the antlib tasks probably need to be updated to allow
>>>> extra files to be attached when install/deploying and then ant
>>>> folks should be sorted... well, that and if they implement a
>>>> task or macro to sign stuff.
>>> we're note even using the antlibs, they were not really working
>>> out. It was easier to just exec the mvn script directly. If Maven
>>> has the command line option to do what we want, then we can do it.
>>
>> Just curious, what wasn't working out with the antlibs? They
>> should prolly be fixed if they are not usable by ant projects.
>>
>>
>>> So if you show me the "$MAVEN_HOME/bin/mvn" command to publish a
>>> single JAR(with a POM) and being able to make sure the signature
>>> goes with it, then we are fine.
>>> GPG signing is a no brainer, we can do that any day.
>>
>> Hrm... I'm not sure there exists such a command at the moment,
>> though its probably easy enough to craft a simple goal to
>> implement what you need.
> yeah, I might just implement this in ANT all together, and skip
> maven, if it is a simple SCP copy.
>>
>> The reason it doesn't work asis, is that the gpg .asc stuff is
>> attached to the current projects artifact and the install/deploy
>> will handle the primary artifact and then any attached artifacts
>> separately. The install-file/deploy-file goals don't have a
>> project to work on so there is nothing to attach to.
>>
>> I suppose that either install-file/deploy-file need to take an
>> additional csv list of other files to "attach" or perhaps simply
>> craft a pom.xml which uses build-helper:attach-artifact ( http://
>> mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-
>> mojo.html ) and dance around mvn a little to make `mvn deploy` work.
>>
>> But, it would really be better IMO, to use the <deploy> task and
>> update the task to have a nested set of <attached-file> elements
>> which can be used to effectively behave the same as mvn would
>> normally by deploying the primary artifact, and then any attached
>> artifacts. Thats *much* less of a hack.
>>
>> Can you tell me why the antlib tasks aren't working for you?
> there were a few things
> 1. documentation or my inability to work with it
> 2. learning curve, I'm trying to do something really simple
> 3. SCP with maven on windows simply didn't work, turns out that it
> still doesn't work when using the command line arguments, so I am
> still running from linux.
>
> since all I wanna do is SCP a .jar .pom .md5 and .asc, why does
> this have to be so complicated :)
> if I can reverse engineer what it is Maven is doing when publishing
> a file to a repo, it will be easier for me to implement it in pure
> ant.
>
> Filip
>>
>> --jason
>>
>>
>> --No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.5.446 / Virus Database: 268.18.18/734 - Release Date:
>> 3/26/2007 2:31 PM
>>
>>
>
Re: Tomcat m2 repo?
Posted by Jason Dillon <ja...@planet57.com>.
On Mar 29, 2007, at 6:39 AM, Filip Hanik - Dev Lists wrote:
>> Hrm... I'm not sure there exists such a command at the moment,
>> though its probably easy enough to craft a simple goal to
>> implement what you need.
> yeah, I might just implement this in ANT all together, and skip
> maven, if it is a simple SCP copy.
You could do that, though IMO it would be a little better to just get
the Maven antlib tasks fixed to allow you to attach artifacts...
which I believe other projects will also need.
>> The reason it doesn't work asis, is that the gpg .asc stuff is
>> attached to the current projects artifact and the install/deploy
>> will handle the primary artifact and then any attached artifacts
>> separately. The install-file/deploy-file goals don't have a
>> project to work on so there is nothing to attach to.
>>
>> I suppose that either install-file/deploy-file need to take an
>> additional csv list of other files to "attach" or perhaps simply
>> craft a pom.xml which uses build-helper:attach-artifact ( http://
>> mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-
>> mojo.html ) and dance around mvn a little to make `mvn deploy` work.
>>
>> But, it would really be better IMO, to use the <deploy> task and
>> update the task to have a nested set of <attached-file> elements
>> which can be used to effectively behave the same as mvn would
>> normally by deploying the primary artifact, and then any attached
>> artifacts. Thats *much* less of a hack.
>>
>> Can you tell me why the antlib tasks aren't working for you?
> there were a few things
> 1. documentation or my inability to work with it
I understand what you mean... the docs are a bit hard to grok. Would
have been nice to see docs in the same style as the Ant manual.
> 2. learning curve, I'm trying to do something really simple
Its relatively simply, though there are a few wrinkles.
First you need to make sure that the wagon provider that you are
using is installed. For example, the Codehaus uses webdav, so for
projects there they need to:
<artifact:install-provider artifactId="wagon-webdav"
version="1.0-beta-2"/>
But, for ASF projects you probably just want the ssh impl:
<artifact:install-provider artifactId="wagon-ssh" version="1.0-
beta-2"/>
Or perhaps the ssh-external version:
<artifact:install-provider artifactId="wagon-ssh-external"
version="1.0-beta-2"/>
I would recommend using "wagon-ssh" if you can so you don't have to
worry about having any specific native executables on your path/etc.
Then you need to configure the authentication in ~/.m2/settings.xml,
which is the same which is used by Maven. If you follow the same
server id's as the ASF pom does then somehing like:
----8<----
<?xml version="1.0"?>
<settings>
<servers>
<server>
<id>apache.snapshots</id>
<username>YOUR_USERNAME</username>
<directoryPermissions>775</directoryPermissions>
<filePermissions>664</filePermissions>
</server>
<server>
<id>apache.releases</id>
<username>YOUR_USERNAME</username>
<directoryPermissions>775</directoryPermissions>
<filePermissions>664</filePermissions>
</server>
</servers>
</settings>
---->8----
Obviously changing YOUR_USERNAME with what is appropriate for your
account on people.apache.org. You will probably need to configure
either a <password> or a <passphrase> for each of the server's
depending on how you have configured access via SSH.
And then you need pom's for each of your artifacts, and in those poms
you should include a <distributionManagement> section to configure
where to deploy to, like:
----8<----
<distributionManagement>
<repository>
<id>apache.releases</id>
<name>Apache Release Distribution Repository</name>
<url>scp://people.apache.org/www/people.apache.org/repo/
m2-ibiblio-rsync-repository</url>
</repository>
<snapshotRepository>
<id>apache.snapshots</id>
<name>Apache Development Snapshot Repository</name>
<url>scp://people.apache.org/www/people.apache.org/repo/
m2-snapshot-repository</url>
</snapshotRepository>
</distributionManagement>
---->8----
I'm not 100% sure, but the Maven antlib tasks _might_ use the normal
parent pom inclusion bits, in which case all you need to do is make
sure that your top-level pom uses the ASF pom as its parent:
----8<----
<parent>
<groupId>org.apache</groupId>
<artifactId>apache</artifactId>
<version>4</version>
</parent>
---->8----
This should get the default <distributionManagement> configuration
into your poms.
And then you just need to <artifact:deploy> with a reference to the
artifact's file and its pom. The artifact will be deployed with the
version information in the referenced pom and will be deployed to
either the <repository> or <snapshotRepository> as configured in the
poms <distributionManagement>.
> 3. SCP with maven on windows simply didn't work, turns out that it
> still doesn't work when using the command line arguments, so I am
> still running from linux.
Weird... not sure that is related to Maven :-P What didn't work, did
it spit out any errors? It *should* work if things are configured
properly.
> since all I wanna do is SCP a .jar .pom .md5 and .asc, why does
> this have to be so complicated :)
Well, its not all that complicated :-P It just requires a wee bit of
configuration to make it work. For most Maven projects this just one
of those things you have to do (configure the wagon impl, setup the
distributionManagement, etc... though much of that can be done once
and then simply inherited. The trickiest part IMO (maven or ant) is
making sure you setup ~/.m2/settings.xml. This is generally a one
time thing for each user... just set it up once and forget about it.
I'm not sure that doing this directly with Ant would be any less
complex. You still need to add stuff to configure where stuff goes,
and then tasks to make it go there, and then abstract the user
authentication bits... so its about the same amount of work.
> if I can reverse engineer what it is Maven is doing when publishing
> a file to a repo, it will be easier for me to implement it in pure
> ant.
Yup you could... though chances are you will find that a wee bit
frustrating, since its all componentized over several different
projects.
IMO, you are better off using the Maven antlib tasks. I just cracked
open the src of these puppies and it looks like it should be simple
to add some additional configuration for attached artifacts. Then
you would just have to create the .asc for each artifact, then
something like:
<artifact:deploy file="somefile.jar" pom="somefile.pom">
<attach file="somefile.jar.asc"/>
<attach file="somefile.pom.asc"/>
</artifact:deploy>
They are going to be releasing a new set of tasks soon to sync up
with the latest Maven 2.0.6 release. The code to add support for
attaching files is trivial, so I'm going to patch it and hopefully
this will get into the release next week.
--jason
Re: Tomcat m2 repo?
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Jason Dillon wrote:
> On Mar 27, 2007, at 4:50 PM, Filip Hanik - Dev Lists wrote:
>>> I don't expect that Tomcat will switch to m2, though if they are
>>> gonna be publishing m2 repos they should use the m2 antlib for
>>> that. But, looks like the m2 antlib is not up to snuff wrt the new?
>>> apache requirements to publish .asc files for releases. I think the
>>> antlib tasks probably need to be updated to allow extra files to be
>>> attached when install/deploying and then ant folks should be
>>> sorted... well, that and if they implement a task or macro to sign
>>> stuff.
>> we're note even using the antlibs, they were not really working out.
>> It was easier to just exec the mvn script directly. If Maven has the
>> command line option to do what we want, then we can do it.
>
> Just curious, what wasn't working out with the antlibs? They should
> prolly be fixed if they are not usable by ant projects.
>
>
>> So if you show me the "$MAVEN_HOME/bin/mvn" command to publish a
>> single JAR(with a POM) and being able to make sure the signature goes
>> with it, then we are fine.
>> GPG signing is a no brainer, we can do that any day.
>
> Hrm... I'm not sure there exists such a command at the moment, though
> its probably easy enough to craft a simple goal to implement what you
> need.
yeah, I might just implement this in ANT all together, and skip maven,
if it is a simple SCP copy.
>
> The reason it doesn't work asis, is that the gpg .asc stuff is
> attached to the current projects artifact and the install/deploy will
> handle the primary artifact and then any attached artifacts
> separately. The install-file/deploy-file goals don't have a project
> to work on so there is nothing to attach to.
>
> I suppose that either install-file/deploy-file need to take an
> additional csv list of other files to "attach" or perhaps simply craft
> a pom.xml which uses build-helper:attach-artifact (
> http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
> ) and dance around mvn a little to make `mvn deploy` work.
>
> But, it would really be better IMO, to use the <deploy> task and
> update the task to have a nested set of <attached-file> elements which
> can be used to effectively behave the same as mvn would normally by
> deploying the primary artifact, and then any attached artifacts.
> Thats *much* less of a hack.
>
> Can you tell me why the antlib tasks aren't working for you?
there were a few things
1. documentation or my inability to work with it
2. learning curve, I'm trying to do something really simple
3. SCP with maven on windows simply didn't work, turns out that it still
doesn't work when using the command line arguments, so I am still
running from linux.
since all I wanna do is SCP a .jar .pom .md5 and .asc, why does this
have to be so complicated :)
if I can reverse engineer what it is Maven is doing when publishing a
file to a repo, it will be easier for me to implement it in pure ant.
Filip
>
> --jason
>
>
> --No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.18/734 - Release Date:
> 3/26/2007 2:31 PM
>
>
Re: Tomcat m2 repo?
Posted by Jason Dillon <ja...@planet57.com>.
On Mar 27, 2007, at 4:50 PM, Filip Hanik - Dev Lists wrote:
>> I don't expect that Tomcat will switch to m2, though if they are
>> gonna be publishing m2 repos they should use the m2 antlib for
>> that. But, looks like the m2 antlib is not up to snuff wrt the
>> new? apache requirements to publish .asc files for releases. I
>> think the antlib tasks probably need to be updated to allow extra
>> files to be attached when install/deploying and then ant folks
>> should be sorted... well, that and if they implement a task or
>> macro to sign stuff.
> we're note even using the antlibs, they were not really working
> out. It was easier to just exec the mvn script directly. If Maven
> has the command line option to do what we want, then we can do it.
Just curious, what wasn't working out with the antlibs? They should
prolly be fixed if they are not usable by ant projects.
> So if you show me the "$MAVEN_HOME/bin/mvn" command to publish a
> single JAR(with a POM) and being able to make sure the signature
> goes with it, then we are fine.
> GPG signing is a no brainer, we can do that any day.
Hrm... I'm not sure there exists such a command at the moment, though
its probably easy enough to craft a simple goal to implement what you
need.
The reason it doesn't work asis, is that the gpg .asc stuff is
attached to the current projects artifact and the install/deploy will
handle the primary artifact and then any attached artifacts
separately. The install-file/deploy-file goals don't have a project
to work on so there is nothing to attach to.
I suppose that either install-file/deploy-file need to take an
additional csv list of other files to "attach" or perhaps simply
craft a pom.xml which uses build-helper:attach-artifact ( http://
mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-
mojo.html ) and dance around mvn a little to make `mvn deploy` work.
But, it would really be better IMO, to use the <deploy> task and
update the task to have a nested set of <attached-file> elements
which can be used to effectively behave the same as mvn would
normally by deploying the primary artifact, and then any attached
artifacts. Thats *much* less of a hack.
Can you tell me why the antlib tasks aren't working for you?
--jason
Re: Tomcat m2 repo?
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Jason Dillon wrote:
> On Mar 27, 2007, at 4:04 PM, Dain Sundstrom wrote:
>> On Mar 27, 2007, at 2:54 PM, Jason Dillon wrote:
>>> On Mar 27, 2007, at 1:58 PM, Filip Hanik - Dev Lists wrote:
>>>>>> Yesterday they marked the issue as resolved since the tomcat jars
>>>>>> are
>>>>>> now available at http://tomcat.apache.org/dev/dist/m2-repository,
>>>>>> but
>>>>>
>>>>> Ug... why on earth is Tomcat not just using the standard Maven 2
>>>>> repos that the rest of us have to use? This is so annoying. If
>>>>> they just published to m2-ibiblio-rsync-repository then they would
>>>>> be done already.
>>>> wow, you're such a joy to be around ;)
>>>
>>> Sorry, this repo stuff is a sore subject for me. I've been trying
>>> to keep things orderly (and limited) and new repos just keep poping
>>> up and into our build. This has been going on for a while now,
>>> though it has gotten better.
>>>
>>> Anyways, nothing personal... I am just a little annoyed with all the
>>> repo related issues in whole.
>>
>> If you remember back, Ant was originally developed to build Tomcat,
>> so the odds of them dropping Ant are pretty slim. Now they maybe
>> willing to add the maven ant tasks to publish to the maven repo, but
>> I suggest you ask really nicely.
>
> I don't expect that Tomcat will switch to m2, though if they are gonna
> be publishing m2 repos they should use the m2 antlib for that. But,
> looks like the m2 antlib is not up to snuff wrt the new? apache
> requirements to publish .asc files for releases. I think the antlib
> tasks probably need to be updated to allow extra files to be attached
> when install/deploying and then ant folks should be sorted... well,
> that and if they implement a task or macro to sign stuff.
we're note even using the antlibs, they were not really working out. It
was easier to just exec the mvn script directly. If Maven has the
command line option to do what we want, then we can do it.
So if you show me the "$MAVEN_HOME/bin/mvn" command to publish a single
JAR(with a POM) and being able to make sure the signature goes with it,
then we are fine.
GPG signing is a no brainer, we can do that any day.
Filip
>
>
> Anyways, I didn't mean to ruffle any feathers, I was just frustrated...
>
> --jason
>
>
>
>
> --No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.18/734 - Release Date:
> 3/26/2007 2:31 PM
>
>
Re: Tomcat m2 repo?
Posted by Jason Dillon <ja...@planet57.com>.
On Mar 27, 2007, at 4:04 PM, Dain Sundstrom wrote:
> On Mar 27, 2007, at 2:54 PM, Jason Dillon wrote:
>> On Mar 27, 2007, at 1:58 PM, Filip Hanik - Dev Lists wrote:
>>>>> Yesterday they marked the issue as resolved since the tomcat
>>>>> jars are
>>>>> now available at http://tomcat.apache.org/dev/dist/m2-
>>>>> repository, but
>>>>
>>>> Ug... why on earth is Tomcat not just using the standard Maven 2
>>>> repos that the rest of us have to use? This is so annoying.
>>>> If they just published to m2-ibiblio-rsync-repository then they
>>>> would be done already.
>>> wow, you're such a joy to be around ;)
>>
>> Sorry, this repo stuff is a sore subject for me. I've been trying
>> to keep things orderly (and limited) and new repos just keep
>> poping up and into our build. This has been going on for a while
>> now, though it has gotten better.
>>
>> Anyways, nothing personal... I am just a little annoyed with all
>> the repo related issues in whole.
>
> If you remember back, Ant was originally developed to build Tomcat,
> so the odds of them dropping Ant are pretty slim. Now they maybe
> willing to add the maven ant tasks to publish to the maven repo,
> but I suggest you ask really nicely.
I don't expect that Tomcat will switch to m2, though if they are
gonna be publishing m2 repos they should use the m2 antlib for that.
But, looks like the m2 antlib is not up to snuff wrt the new? apache
requirements to publish .asc files for releases. I think the antlib
tasks probably need to be updated to allow extra files to be attached
when install/deploying and then ant folks should be sorted... well,
that and if they implement a task or macro to sign stuff.
Anyways, I didn't mean to ruffle any feathers, I was just frustrated...
--jason
Re: Tomcat m2 repo?
Posted by Dain Sundstrom <da...@iq80.com>.
On Mar 27, 2007, at 2:54 PM, Jason Dillon wrote:
> On Mar 27, 2007, at 1:58 PM, Filip Hanik - Dev Lists wrote:
>>>> Yesterday they marked the issue as resolved since the tomcat
>>>> jars are
>>>> now available at http://tomcat.apache.org/dev/dist/m2-
>>>> repository, but
>>>
>>> Ug... why on earth is Tomcat not just using the standard Maven 2
>>> repos that the rest of us have to use? This is so annoying. If
>>> they just published to m2-ibiblio-rsync-repository then they
>>> would be done already.
>> wow, you're such a joy to be around ;)
>
> Sorry, this repo stuff is a sore subject for me. I've been trying
> to keep things orderly (and limited) and new repos just keep poping
> up and into our build. This has been going on for a while now,
> though it has gotten better.
>
> Anyways, nothing personal... I am just a little annoyed with all
> the repo related issues in whole.
If you remember back, Ant was originally developed to build Tomcat,
so the odds of them dropping Ant are pretty slim. Now they maybe
willing to add the maven ant tasks to publish to the maven repo, but
I suggest you ask really nicely.
-dain
Re: Tomcat m2 repo?
Posted by Jason Dillon <ja...@planet57.com>.
On Mar 27, 2007, at 1:58 PM, Filip Hanik - Dev Lists wrote:
>>> Yesterday they marked the issue as resolved since the tomcat jars
>>> are
>>> now available at http://tomcat.apache.org/dev/dist/m2-repository,
>>> but
>>
>> Ug... why on earth is Tomcat not just using the standard Maven 2
>> repos that the rest of us have to use? This is so annoying. If
>> they just published to m2-ibiblio-rsync-repository then they would
>> be done already.
> wow, you're such a joy to be around ;)
Sorry, this repo stuff is a sore subject for me. I've been trying to
keep things orderly (and limited) and new repos just keep poping up
and into our build. This has been going on for a while now, though
it has gotten better.
Anyways, nothing personal... I am just a little annoyed with all the
repo related issues in whole.
>> Blah... I assume this is an Ant-based project? So either write a
>> small task to invoke gpg (peep at how the mvn plugin works for
>> where to start http://svn.apache.org/repos/asf/maven/plugins/trunk/
>> maven-gpg-plugin/), or write a macro to invoke an exec task def to
>> invoke gpg to sign things.
> we can do all that, but there was no way to get the .asc file to
> travel up to the repo with the JAR/POM. Not even using the mvn
> command line
Would be nice if the m2 antlib tasks helped you do this... but if
not, we can always role a custom m2 plugin to make it work. Though
thats only a short-term solution, longer-term if you are gonna use
the m2 antlib tasks, then we should get those with the features you
need.
--jason
Re: Tomcat m2 repo?
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Jason Dillon wrote:
> On Mar 27, 2007, at 8:04 AM, Paul McMahan wrote:
>
>> A few months ago I opened a tomcat issue requesting them to publish
>> the tomcat jars to a maven repo.
>> http://issues.apache.org/bugzilla/show_bug.cgi?id=41093
>>
>> Yesterday they marked the issue as resolved since the tomcat jars are
>> now available at http://tomcat.apache.org/dev/dist/m2-repository, but
>
> Ug... why on earth is Tomcat not just using the standard Maven 2 repos
> that the rest of us have to use? This is so annoying. If they just
> published to m2-ibiblio-rsync-repository then they would be done already.
wow, you're such a joy to be around ;)
>
>
>> commented that they would publish to central if there is a way to work
>> around a problem with PGP signatures:
>>
>>> Doesn't seem like I can publish to the central repo
>>> because it requires PGP signatures and maven
>>> doesn't let you do that with single JAR if you're not
>>> building with Maven.
>>>
>>> If you have a way to get the PGP info in there in
>>> the way we are doing it now, let us know and
>>> open a new bug.
>>
>> If anyone knows of a way to sign single JARs not built with maven then
>> please enlighten us or just go ahead open a new tomcat bug with the
>> details. This may be the only remaining impediment towards making the
>> tomcat jars available on central.
>
> Blah... I assume this is an Ant-based project? So either write a
> small task to invoke gpg (peep at how the mvn plugin works for where
> to start
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-gpg-plugin/),
> or write a macro to invoke an exec task def to invoke gpg to sign things.
we can do all that, but there was no way to get the .asc file to travel
up to the repo with the JAR/POM. Not even using the mvn command line
>
> Then just use the Maven antlib tasks to deploy each file one by one...
> and if you find that doesn't work, then implement your own scp to
> install the files and/or complain to the mvn team to add support for
> better ant-based deployment. Or just switch to Maven.
>
> Either way, they should be able to do all of this by hand to get
> around any current issues they have with their lack of build
> expertise. Highly annoyed that we have waited so long for them to
> basically do nothing.
whatever
>
> --jason
>
>
>
>>
>> Best wishes,
>> Paul
>>
>>
>> On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
>>> Okay, hopefully they will get the kinks out soon ;-)
>>>
>>> --jason
>>>
>>>
>>> On Feb 13, 2007, at 4:39 PM, Paul McMahan wrote:
>>>
>>> > Tomcat currently builds with ant and then manually publish their jars
>>> > to a repo at tomcat.apache.org. See
>>> > http://www.nabble.com/Tomcat-Jars---Maven2-repo-
>>> > tf3023226.html#a8397986
>>> > They have only just started to make publishing to an m2 repo part of
>>> > their release process, and IIUC they want to work the kinks out of
>>> > their scripts before pointing them at central.
>>> >
>>> > Best wishes,
>>> > Paul
>>> >
>>> > On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
>>> >> Why do we need this repo:
>>> >>
>>> >> http://tomcat.apache.org/dev/dist/m2-repository
>>> >>
>>> >> Is Tomcat not publishing to central? If not... anyone know why?
>>> >>
>>> >> --jason
>>> >>
>>>
>>>
>
>
>
> --No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.18/734 - Release Date:
> 3/26/2007 2:31 PM
>
>
Re: Tomcat m2 repo?
Posted by Jason Dillon <ja...@planet57.com>.
On Mar 27, 2007, at 8:04 AM, Paul McMahan wrote:
> A few months ago I opened a tomcat issue requesting them to publish
> the tomcat jars to a maven repo.
> http://issues.apache.org/bugzilla/show_bug.cgi?id=41093
>
> Yesterday they marked the issue as resolved since the tomcat jars are
> now available at http://tomcat.apache.org/dev/dist/m2-repository, but
Ug... why on earth is Tomcat not just using the standard Maven 2
repos that the rest of us have to use? This is so annoying. If
they just published to m2-ibiblio-rsync-repository then they would be
done already.
> commented that they would publish to central if there is a way to work
> around a problem with PGP signatures:
>
>> Doesn't seem like I can publish to the central repo
>> because it requires PGP signatures and maven
>> doesn't let you do that with single JAR if you're not
>> building with Maven.
>>
>> If you have a way to get the PGP info in there in
>> the way we are doing it now, let us know and
>> open a new bug.
>
> If anyone knows of a way to sign single JARs not built with maven then
> please enlighten us or just go ahead open a new tomcat bug with the
> details. This may be the only remaining impediment towards making the
> tomcat jars available on central.
Blah... I assume this is an Ant-based project? So either write a
small task to invoke gpg (peep at how the mvn plugin works for where
to start http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-
gpg-plugin/), or write a macro to invoke an exec task def to invoke
gpg to sign things.
Then just use the Maven antlib tasks to deploy each file one by
one... and if you find that doesn't work, then implement your own scp
to install the files and/or complain to the mvn team to add support
for better ant-based deployment. Or just switch to Maven.
Either way, they should be able to do all of this by hand to get
around any current issues they have with their lack of build
expertise. Highly annoyed that we have waited so long for them to
basically do nothing.
--jason
>
> Best wishes,
> Paul
>
>
> On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
>> Okay, hopefully they will get the kinks out soon ;-)
>>
>> --jason
>>
>>
>> On Feb 13, 2007, at 4:39 PM, Paul McMahan wrote:
>>
>> > Tomcat currently builds with ant and then manually publish their
>> jars
>> > to a repo at tomcat.apache.org. See
>> > http://www.nabble.com/Tomcat-Jars---Maven2-repo-
>> > tf3023226.html#a8397986
>> > They have only just started to make publishing to an m2 repo
>> part of
>> > their release process, and IIUC they want to work the kinks out of
>> > their scripts before pointing them at central.
>> >
>> > Best wishes,
>> > Paul
>> >
>> > On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
>> >> Why do we need this repo:
>> >>
>> >> http://tomcat.apache.org/dev/dist/m2-repository
>> >>
>> >> Is Tomcat not publishing to central? If not... anyone know why?
>> >>
>> >> --jason
>> >>
>>
>>
Re: Tomcat m2 repo?
Posted by Jason Dillon <ja...@planet57.com>.
Are you guys using the m2 antlib tasks to deploy?
--jason
On Mar 27, 2007, at 2:02 PM, Filip Hanik - Dev Lists wrote:
> if PGP signatures in form of .asc are not required, then we can
> switch to the new repo anytime
>
> Filip
>
> Jeff Genender wrote:
>> Why do they need pgp signatures? That is new to me.
>>
>> Do you mean SHA1 signatures?
>>
>> For SHA1 sigs, they can use the sha1 program on minotaur.
>>
>> They would need to do something like:
>>
>> sha1 -q ./tomcat-whatever.jar > ./timcat-whatever.jar.sha1
>> sha1 -q ./tomcat-whatever.pom > ./timcat-whatever.pom.sha1
>>
>> Jeff
>>
>>
>> Paul McMahan wrote:
>>
>>> A few months ago I opened a tomcat issue requesting them to publish
>>> the tomcat jars to a maven repo.
>>> http://issues.apache.org/bugzilla/show_bug.cgi?id=41093
>>>
>>> Yesterday they marked the issue as resolved since the tomcat jars
>>> are
>>> now available at http://tomcat.apache.org/dev/dist/m2-repository,
>>> but
>>> commented that they would publish to central if there is a way to
>>> work
>>> around a problem with PGP signatures:
>>>
>>>
>>>> Doesn't seem like I can publish to the central repo
>>>> because it requires PGP signatures and maven
>>>> doesn't let you do that with single JAR if you're not
>>>> building with Maven.
>>>>
>>>> If you have a way to get the PGP info in there in
>>>> the way we are doing it now, let us know and
>>>> open a new bug.
>>>>
>>> If anyone knows of a way to sign single JARs not built with maven
>>> then
>>> please enlighten us or just go ahead open a new tomcat bug with the
>>> details. This may be the only remaining impediment towards
>>> making the
>>> tomcat jars available on central.
>>>
>>> Best wishes,
>>> Paul
>>>
>>>
>>> On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
>>>
>>>> Okay, hopefully they will get the kinks out soon ;-)
>>>>
>>>> --jason
>>>>
>>>>
>>>> On Feb 13, 2007, at 4:39 PM, Paul McMahan wrote:
>>>>
>>>>
>>>>> Tomcat currently builds with ant and then manually publish
>>>>> their jars
>>>>> to a repo at tomcat.apache.org. See
>>>>> http://www.nabble.com/Tomcat-Jars---Maven2-repo-
>>>>> tf3023226.html#a8397986
>>>>> They have only just started to make publishing to an m2 repo
>>>>> part of
>>>>> their release process, and IIUC they want to work the kinks out of
>>>>> their scripts before pointing them at central.
>>>>>
>>>>> Best wishes,
>>>>> Paul
>>>>>
>>>>> On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
>>>>>
>>>>>> Why do we need this repo:
>>>>>>
>>>>>> http://tomcat.apache.org/dev/dist/m2-repository
>>>>>>
>>>>>> Is Tomcat not publishing to central? If not... anyone know why?
>>>>>>
>>>>>> --jason
>>>>>>
>>>>>>
>>>>
>>
>>
>>
>
Re: Tomcat m2 repo?
Posted by Davanum Srinivas <da...@gmail.com>.
Filip,
For the snapshots, yes, it's not mandatory. We usually drop the snapshots here:
http://people.apache.org/repo/m2-snapshot-repository/
It would be great to have it in that repo.
thanks,
dims
On 3/27/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
> if PGP signatures in form of .asc are not required, then we can switch
> to the new repo anytime
>
> Filip
>
> Jeff Genender wrote:
> > Why do they need pgp signatures? That is new to me.
> >
> > Do you mean SHA1 signatures?
> >
> > For SHA1 sigs, they can use the sha1 program on minotaur.
> >
> > They would need to do something like:
> >
> > sha1 -q ./tomcat-whatever.jar > ./timcat-whatever.jar.sha1
> > sha1 -q ./tomcat-whatever.pom > ./timcat-whatever.pom.sha1
> >
> > Jeff
> >
> >
> > Paul McMahan wrote:
> >
> >> A few months ago I opened a tomcat issue requesting them to publish
> >> the tomcat jars to a maven repo.
> >> http://issues.apache.org/bugzilla/show_bug.cgi?id=41093
> >>
> >> Yesterday they marked the issue as resolved since the tomcat jars are
> >> now available at http://tomcat.apache.org/dev/dist/m2-repository, but
> >> commented that they would publish to central if there is a way to work
> >> around a problem with PGP signatures:
> >>
> >>
> >>> Doesn't seem like I can publish to the central repo
> >>> because it requires PGP signatures and maven
> >>> doesn't let you do that with single JAR if you're not
> >>> building with Maven.
> >>>
> >>> If you have a way to get the PGP info in there in
> >>> the way we are doing it now, let us know and
> >>> open a new bug.
> >>>
> >> If anyone knows of a way to sign single JARs not built with maven then
> >> please enlighten us or just go ahead open a new tomcat bug with the
> >> details. This may be the only remaining impediment towards making the
> >> tomcat jars available on central.
> >>
> >> Best wishes,
> >> Paul
> >>
> >>
> >> On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
> >>
> >>> Okay, hopefully they will get the kinks out soon ;-)
> >>>
> >>> --jason
> >>>
> >>>
> >>> On Feb 13, 2007, at 4:39 PM, Paul McMahan wrote:
> >>>
> >>>
> >>>> Tomcat currently builds with ant and then manually publish their jars
> >>>> to a repo at tomcat.apache.org. See
> >>>> http://www.nabble.com/Tomcat-Jars---Maven2-repo-
> >>>> tf3023226.html#a8397986
> >>>> They have only just started to make publishing to an m2 repo part of
> >>>> their release process, and IIUC they want to work the kinks out of
> >>>> their scripts before pointing them at central.
> >>>>
> >>>> Best wishes,
> >>>> Paul
> >>>>
> >>>> On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
> >>>>
> >>>>> Why do we need this repo:
> >>>>>
> >>>>> http://tomcat.apache.org/dev/dist/m2-repository
> >>>>>
> >>>>> Is Tomcat not publishing to central? If not... anyone know why?
> >>>>>
> >>>>> --jason
> >>>>>
> >>>>>
> >>>
> >
> >
> >
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
Re: Tomcat m2 repo?
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
if PGP signatures in form of .asc are not required, then we can switch
to the new repo anytime
Filip
Jeff Genender wrote:
> Why do they need pgp signatures? That is new to me.
>
> Do you mean SHA1 signatures?
>
> For SHA1 sigs, they can use the sha1 program on minotaur.
>
> They would need to do something like:
>
> sha1 -q ./tomcat-whatever.jar > ./timcat-whatever.jar.sha1
> sha1 -q ./tomcat-whatever.pom > ./timcat-whatever.pom.sha1
>
> Jeff
>
>
> Paul McMahan wrote:
>
>> A few months ago I opened a tomcat issue requesting them to publish
>> the tomcat jars to a maven repo.
>> http://issues.apache.org/bugzilla/show_bug.cgi?id=41093
>>
>> Yesterday they marked the issue as resolved since the tomcat jars are
>> now available at http://tomcat.apache.org/dev/dist/m2-repository, but
>> commented that they would publish to central if there is a way to work
>> around a problem with PGP signatures:
>>
>>
>>> Doesn't seem like I can publish to the central repo
>>> because it requires PGP signatures and maven
>>> doesn't let you do that with single JAR if you're not
>>> building with Maven.
>>>
>>> If you have a way to get the PGP info in there in
>>> the way we are doing it now, let us know and
>>> open a new bug.
>>>
>> If anyone knows of a way to sign single JARs not built with maven then
>> please enlighten us or just go ahead open a new tomcat bug with the
>> details. This may be the only remaining impediment towards making the
>> tomcat jars available on central.
>>
>> Best wishes,
>> Paul
>>
>>
>> On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
>>
>>> Okay, hopefully they will get the kinks out soon ;-)
>>>
>>> --jason
>>>
>>>
>>> On Feb 13, 2007, at 4:39 PM, Paul McMahan wrote:
>>>
>>>
>>>> Tomcat currently builds with ant and then manually publish their jars
>>>> to a repo at tomcat.apache.org. See
>>>> http://www.nabble.com/Tomcat-Jars---Maven2-repo-
>>>> tf3023226.html#a8397986
>>>> They have only just started to make publishing to an m2 repo part of
>>>> their release process, and IIUC they want to work the kinks out of
>>>> their scripts before pointing them at central.
>>>>
>>>> Best wishes,
>>>> Paul
>>>>
>>>> On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
>>>>
>>>>> Why do we need this repo:
>>>>>
>>>>> http://tomcat.apache.org/dev/dist/m2-repository
>>>>>
>>>>> Is Tomcat not publishing to central? If not... anyone know why?
>>>>>
>>>>> --jason
>>>>>
>>>>>
>>>
>
>
>
Re: Tomcat m2 repo?
Posted by Jeff Genender <jg...@apache.org>.
Why do they need pgp signatures? That is new to me.
Do you mean SHA1 signatures?
For SHA1 sigs, they can use the sha1 program on minotaur.
They would need to do something like:
sha1 -q ./tomcat-whatever.jar > ./timcat-whatever.jar.sha1
sha1 -q ./tomcat-whatever.pom > ./timcat-whatever.pom.sha1
Jeff
Paul McMahan wrote:
> A few months ago I opened a tomcat issue requesting them to publish
> the tomcat jars to a maven repo.
> http://issues.apache.org/bugzilla/show_bug.cgi?id=41093
>
> Yesterday they marked the issue as resolved since the tomcat jars are
> now available at http://tomcat.apache.org/dev/dist/m2-repository, but
> commented that they would publish to central if there is a way to work
> around a problem with PGP signatures:
>
>> Doesn't seem like I can publish to the central repo
>> because it requires PGP signatures and maven
>> doesn't let you do that with single JAR if you're not
>> building with Maven.
>>
>> If you have a way to get the PGP info in there in
>> the way we are doing it now, let us know and
>> open a new bug.
>
> If anyone knows of a way to sign single JARs not built with maven then
> please enlighten us or just go ahead open a new tomcat bug with the
> details. This may be the only remaining impediment towards making the
> tomcat jars available on central.
>
> Best wishes,
> Paul
>
>
> On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
>> Okay, hopefully they will get the kinks out soon ;-)
>>
>> --jason
>>
>>
>> On Feb 13, 2007, at 4:39 PM, Paul McMahan wrote:
>>
>> > Tomcat currently builds with ant and then manually publish their jars
>> > to a repo at tomcat.apache.org. See
>> > http://www.nabble.com/Tomcat-Jars---Maven2-repo-
>> > tf3023226.html#a8397986
>> > They have only just started to make publishing to an m2 repo part of
>> > their release process, and IIUC they want to work the kinks out of
>> > their scripts before pointing them at central.
>> >
>> > Best wishes,
>> > Paul
>> >
>> > On 2/13/07, Jason Dillon <ja...@planet57.com> wrote:
>> >> Why do we need this repo:
>> >>
>> >> http://tomcat.apache.org/dev/dist/m2-repository
>> >>
>> >> Is Tomcat not publishing to central? If not... anyone know why?
>> >>
>> >> --jason
>> >>
>>
>>