You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by Sandro Martini <sa...@gmail.com> on 2009/11/16 11:19:26 UTC
Re: [jira] Commented: (PIVOT-260) Add missing resources in generated
jar files, for compatibility with Apache Maven Repository
Hi Todd,
this week I plan to find some time to do this work:
Add the following files under META-INF:
README, LICENSE, NOTICE, DISCLAIMER, and I'd exclude the RELEASE-NOTES.
But for all our jars, and in standard builds, Ok ?
Because providing additional (maven-only) builds seems complicated to
me (mainly for maintenance), and I don't know it this can cause
problems for publishing them into maven repository ... and only few KB
should be added to jars
Tell me.
Bye
Re: [jira] Commented: (PIVOT-260) Add missing resources in generated
jar files, for compatibility with Apache Maven Repository
Posted by Sandro Martini <sa...@gmail.com>.
Hi Todd,
> No - you'll need to wait until we actually release 1.4. Then, we'll look to
> publish the jars on Maven repositories.
Ok, in the meantime I'll comment and close the issue.
Bye
Re: [jira] Commented: (PIVOT-260) Add missing resources in generated
jar files, for compatibility with Apache Maven Repository
Posted by Todd Volkert <tv...@gmail.com>.
> > Sounds like you can go ahead and resolve the JIRA issue.
> But shouldn't I copy the generated jars to the people server etc etc
> before to close the issue (see bottom) ?
>
No - you'll need to wait until we actually release 1.4. Then, we'll look to
publish the jars on Maven repositories.
-T
Re: [jira] Commented: (PIVOT-260) Add missing resources in generated
jar files, for compatibility with Apache Maven Repository
Posted by Sandro Martini <sa...@gmail.com>.
Hi Todd,
> You can update the README to reference 1.4 - we'll make a deeper sweep of
> the root files when we tag the 1.4 release.
Ok, I'll make it now until i remember it ...
> Sounds like you can go ahead and resolve the JIRA issue.
But shouldn't I copy the generated jars to the people server etc etc
before to close the issue (see bottom) ?
> ASF projects can get their artifacts published in the central Maven repository (eg http://repo2.maven.org/maven2/) by copying them to http://people.apache.org/repo/m2-ibiblio-rsync-repository/ which automatically syncs with the central repo.
> To do that on people.apache.org copy them to /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository.
> All committers should have access to do that, via ssh.
I have it, Ok.
> Each artifact MUST have been voted on by a PMC and comply with all the release requirements like having LICENSE, NOTICE, DISCLAIMER files, be signed, and indicate they're incubating artifacts in the name eg by including the "-incubating" suffix in the artifact name. A common way of getting that vote done is by including the artifacts to be published in a staging area which is pointed to in the release VOTE.
mhhh reading better this probably I'll have to wait for the release
1.4 approved, right (other requirements now should be Ok) ?
Or can I do a "pivot-1.4-incubating_maven_test" folder inside my home
on that server ?
Thanks,
Sandro
Re: [jira] Commented: (PIVOT-260) Add missing resources in generated
jar files, for compatibility with Apache Maven Repository
Posted by Todd Volkert <tv...@gmail.com>.
You can update the README to reference 1.4 - we'll make a deeper sweep of
the root files when we tag the 1.4 release. Sounds like you can go ahead
and resolve the JIRA issue.
-T
On Mon, Nov 16, 2009 at 9:00 AM, Sandro Martini <sa...@gmail.com>wrote:
> Hi,
> > Thanks for tackling this!
> No problem :-)
>
> Update: was (much) simpler than I imagine :-) , I've just committed
> the little change.
> I have tried to run some ant commands on it, and run a test webapp
> with inside our new jars, and all works good (as before).
>
> Only a little question: in the README, there are many references to
> pivot 1.3 , can I make the replace of 1.3 with 1.4 or there is other
> to change/verify in it ?
>
> Other files seems ok, only the license file is a little bigger (34
> KB), but compressed is little (approx. 9 KB).
>
>
> Tell me for problems, or if I can comment the issue in JIRA and
> proceed to the next step, but for this I need some more info from Todd
> (sign jars and copy them by hand to the people server at apache) ...
>
> Bye
>
Re: [jira] Commented: (PIVOT-260) Add missing resources in generated
jar files, for compatibility with Apache Maven Repository
Posted by Sandro Martini <sa...@gmail.com>.
Hi,
> Thanks for tackling this!
No problem :-)
Update: was (much) simpler than I imagine :-) , I've just committed
the little change.
I have tried to run some ant commands on it, and run a test webapp
with inside our new jars, and all works good (as before).
Only a little question: in the README, there are many references to
pivot 1.3 , can I make the replace of 1.3 with 1.4 or there is other
to change/verify in it ?
Other files seems ok, only the license file is a little bigger (34
KB), but compressed is little (approx. 9 KB).
Tell me for problems, or if I can comment the issue in JIRA and
proceed to the next step, but for this I need some more info from Todd
(sign jars and copy them by hand to the people server at apache) ...
Bye
Re: [jira] Commented: (PIVOT-260) Add missing resources in generated
jar files, for compatibility with Apache Maven Repository
Posted by Todd Volkert <tv...@gmail.com>.
Agreed - this should only be something we add to build.xml to augment our
Ant builds.
Thanks for tackling this!
-T
On Mon, Nov 16, 2009 at 5:19 AM, Sandro Martini <sa...@gmail.com>wrote:
> Hi Todd,
> this week I plan to find some time to do this work:
>
> Add the following files under META-INF:
>
> README, LICENSE, NOTICE, DISCLAIMER, and I'd exclude the RELEASE-NOTES.
>
> But for all our jars, and in standard builds, Ok ?
> Because providing additional (maven-only) builds seems complicated to
> me (mainly for maintenance), and I don't know it this can cause
> problems for publishing them into maven repository ... and only few KB
> should be added to jars
>
> Tell me.
>
> Bye
>