[
https://issues.apache.org/jira/browse/PIVOT-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858845#action_12858845
]
Sandro Martini commented on PIVOT-383:
--------------------------------------
For adding (maven-compatible) jars for Pivot Source, I'm thinking to add one
task in our ant build file, like another customized version of the package,
called only when desired. And add the generated jars to the existing
maven-install task.
After this (later ...) I could also add the same for the generation of javadocs
jars (maven compatible too), useful when using Maven for example inside an IDE.
So, using this approach at the moment I'd prefer to not use maven (native)
build files, maybe we could consider this for 2.0, right ?
Tell me something.
> 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.1
>
> Attachments: 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 corrisponding 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/5.1.0.5/
> 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.
