You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2010/04/22 18:45:52 UTC
[jira] Created: (ZOOKEEPER-750) move maven artifacts into
"dist-maven" subdir of the release (package target)
move maven artifacts into "dist-maven" subdir of the release (package target)
-----------------------------------------------------------------------------
Key: ZOOKEEPER-750
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-750
Project: Zookeeper
Issue Type: Bug
Components: build
Affects Versions: 3.3.0
Reporter: Patrick Hunt
Fix For: 3.3.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-750) move maven artifacts into
"dist-maven" subdir of the release (package target)
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-750:
-----------------------------------
Assignee: Patrick Hunt
Description:
The maven artifacts are currently (3.3.0) put into the toplevel of the release. This causes confusion
amonst new users (ie "which jar do I use?"). Also the naming of the bin jar is wrong for maven (to put
onto the maven repo it must be named without the -bin) which adds extra burden for the release
manager. Putting into a subdir fixes this and makes it explicit what's being deployed to maven repo.
> move maven artifacts into "dist-maven" subdir of the release (package target)
> -----------------------------------------------------------------------------
>
> Key: ZOOKEEPER-750
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-750
> Project: Zookeeper
> Issue Type: Bug
> Components: build
> Affects Versions: 3.3.0
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.3.1
>
>
> The maven artifacts are currently (3.3.0) put into the toplevel of the release. This causes confusion
> amonst new users (ie "which jar do I use?"). Also the naming of the bin jar is wrong for maven (to put
> onto the maven repo it must be named without the -bin) which adds extra burden for the release
> manager. Putting into a subdir fixes this and makes it explicit what's being deployed to maven repo.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-750) move maven artifacts into
"dist-maven" subdir of the release (package target)
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-750:
-----------------------------------
Fix Version/s: 3.4.0
> move maven artifacts into "dist-maven" subdir of the release (package target)
> -----------------------------------------------------------------------------
>
> Key: ZOOKEEPER-750
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-750
> Project: Zookeeper
> Issue Type: Bug
> Components: build
> Affects Versions: 3.3.0
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.3.1, 3.4.0
>
>
> The maven artifacts are currently (3.3.0) put into the toplevel of the release. This causes confusion
> amonst new users (ie "which jar do I use?"). Also the naming of the bin jar is wrong for maven (to put
> onto the maven repo it must be named without the -bin) which adds extra burden for the release
> manager. Putting into a subdir fixes this and makes it explicit what's being deployed to maven repo.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ZOOKEEPER-750) move maven artifacts into
"dist-maven" subdir of the release (package target)
Posted by "Henry Robinson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henry Robinson resolved ZOOKEEPER-750.
--------------------------------------
Resolution: Fixed
I just committed ZOOKEEPER-749 (which addresses this as well). Thanks Patrick!
> move maven artifacts into "dist-maven" subdir of the release (package target)
> -----------------------------------------------------------------------------
>
> Key: ZOOKEEPER-750
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-750
> Project: Zookeeper
> Issue Type: Bug
> Components: build
> Affects Versions: 3.3.0
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.3.1, 3.4.0
>
>
> The maven artifacts are currently (3.3.0) put into the toplevel of the release. This causes confusion
> amonst new users (ie "which jar do I use?"). Also the naming of the bin jar is wrong for maven (to put
> onto the maven repo it must be named without the -bin) which adds extra burden for the release
> manager. Putting into a subdir fixes this and makes it explicit what's being deployed to maven repo.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.