pivot-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandro Martini (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIVOT-383) Jars for Sources in Maven Repository
Date Tue, 25 May 2010 13:36:29 GMT

    [ https://issues.apache.org/jira/browse/PIVOT-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871144#action_12871144

Sandro Martini commented on PIVOT-383:

Hi Greg,

> Since the changes to maven-deploy.sh are related to this ticket, I would suggest that
you try to tackle them. 

> The maven-deploy.sh script lives in the infra branch. Note that this script is meant
to be run from the same directory as build.xml. So you'll probably want to add it to your
path in order to test your changes.
Ok but my problem is that i don't have a Mac or a properly Linux machine (i destroy all my
VM last week for a reinstall from scratch with the newer Ubuntu release, and I'll reinstall
them next week, not before ). 
So I'll try to make the changes but I'll ask to you for testing them.


> Jars for Sources in Maven Repository
> ------------------------------------
>                 Key: PIVOT-383
>                 URL: https://issues.apache.org/jira/browse/PIVOT-383
>             Project: Pivot
>          Issue Type: Improvement
>    Affects Versions: 1.4
>            Reporter: Sandro Martini
>            Assignee: Sandro Martini
>            Priority: Minor
>             Fix For: 1.5
>         Attachments: build.xml.patch, maven-pom-that-builds-pivot.patch
> In some cases, it's useful to have jars for sources in Maven Repository, so for example
from the IDE it's possible to download them and have full navigation support on related sources.
> For a sample of jars to be generated (naming convention etc), take a look here:
> http://repo1.maven.org/maven2/org/apache/tapestry/tapestry-core/
> So, we need to modify the build script (only the Maven-related part) to generate the
*sources.jar, and maybe also the script to publish them to the maven repository.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message