Re: September report: draft for review

2017-09-11 Thread Andrei Dulceanu
Looks good to me.

2017-09-11 18:24 GMT+03:00 Cédric Damioli :

>
>
> Le 11/09/2017 à 15:54, Michael Dürig a écrit :
>
>>
>> Hi,
>>
>> I've assembled a preliminary board report for September:
>>
>> https://wiki.apache.org/jackrabbit/Board%20Report%20September%202017
>>
>> Please have a look at let me know of any omissions or corrections. I plan
>> to submit it next Wednesday morning CET.
>>
>> Michael
>>
>>
>> +1
>
> --
> Cédric Damioli
> CMS - Java - Open Source
> www.ametys.org
>
>


AW: [VOTE] Release Apache Jackrabbit 2.14.3

2017-09-11 Thread KÖLL Claus
+1

greets
claus


Re: [IP CLEARANCE][VOTE] FileVault Package Maven Plugin Contribution

2017-09-11 Thread Chetan Mehrotra
+1 Accept FileVault Package Maven Plugin into Apache Jackrabbit

Chetan Mehrotra


On Tue, Sep 12, 2017 at 8:18 AM, Tobias Bocanegra  wrote:
> [ ] +1 Accept FileVault Package Maven Plugin into Apache Jackrabbit
>
>
> Regards, Toby


Re: [IP CLEARANCE][VOTE] FileVault Package Maven Plugin Contribution

2017-09-11 Thread Tobias Bocanegra
[ ] +1 Accept FileVault Package Maven Plugin into Apache Jackrabbit

Regards, Toby


[IP CLEARANCE][VOTE] FileVault Package Maven Plugin Contribution

2017-09-11 Thread Tobias Bocanegra
Hi,

Jackrabbit has received a donation of Adobe's FileVault Package Maven Plugin 
that we'd like
to have as part of the contribs. the process is tracked under JCRVLT-202
and the signed source code is available here:

tar: 
sftp://people.apache.org/home/tripod/contributions/jackrabbit-filevault-package-plugin.tgz
sha1: 990a6120fd0470273c097067c22015870172469a

The IP Clearance document:
https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/jackrabbit-filevault-package-plugin.xml

Note that we intend to place the code below
https://svn.apache.org/repos/asf/jackrabbit/commons/filevault-package-maven-plugin/

Please vote to approve this contribution.  Lazy consensus applies: if
no -1 votes are cast

within the next 72 hours, the vote passes.

[ ] +1 Accept FileVault into Apache Jackrabbit
[ ] -1 Reject the contribution because...

regards, toby




[jira] [Commented] (JCRVLT-202) Import Adobe's content package maven plugin

2017-09-11 Thread Tobias Bocanegra (JIRA)

[ 
https://issues.apache.org/jira/browse/JCRVLT-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162381#comment-16162381
 ] 

Tobias Bocanegra commented on JCRVLT-202:
-

reverted the commit in 1808077, due to lack of ip clearance

> Import Adobe's content package maven plugin
> ---
>
> Key: JCRVLT-202
> URL: https://issues.apache.org/jira/browse/JCRVLT-202
> Project: Jackrabbit FileVault
>  Issue Type: Task
>  Components: package maven plugin
>Reporter: Tobias Bocanegra
>Assignee: Tobias Bocanegra
> Fix For: package-maven-plugin-1.0.0
>
>
> The content-package maven plugin is a maven plugin that simplifies the 
> creation of content package maven artifacts. The content packages can later 
> be used to install content into a JCR repository using the Apache Jackrabbit 
> FileVault packaging runtime.
> Filevault was contributed 4 years ago, but we never had a tool to create the 
> packaged during runtime. Adobe's plugin is publicly available, but only in 
> binary form. With this contribution, we want to bring the source and 
> development closer to the filevault core and to leverage the community better 
> in driving this plugin further.
> *details*
> java package space: 
> {code}
> org.apache.jackrabbit.filevault.maven.packaging
> {code}
> plugin name:
> {code}
> org.apache.jackrabbit.filevault
> package-maven-plugin
> {code}
> scm location: 
> - a) SVN: 
> https://svn.apache.org/repos/asf/jackrabbit/commons/package-maven-plugin
> - b) GIT: 
> https://git-wip-us.apache.org/repos/asf?p=jackrabbit-filevault-package-plugin.git;a=tree



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Committership under a Corporate CLA

2017-09-11 Thread Tobias Bocanegra
Hi,

I'm filling in the IP clearance template [1] for the FileVault Package Plugin
contribution by Adobe Systems as recorded in JCRVLT-202. One of the
required steps is reminding active committers about their
responsibilities regarding Corporate CLAs:

Remind active committers that they are responsible for
ensuring that a Corporate CLA is recorded if such is
required to authorize their contributions under their
individual CLA.

Essentially, if you're working on Jackrabbit code and committing your
changes back as a part of your job, you need to make sure that the
appropriate Corporate CLA has been recorded and that you are covered
by it. Let me know if you're not sure about your status regarding
this, so I can help figure out if some actions are needed.

Regards,
Toby

[1] http://incubator.apache.org/ip-clearance/ip-clearance-template.htm



Re: Donation of Adobe's content-package-maven-plugin

2017-09-11 Thread Stian Soiland-Reyes
Thanks! Personally I don't think 40 or so files is little code, although of
course large parts of that are tests and beans so that is for the PMC to
decide :-)

>From a brief look at the code it looks clean, but I don't know the origin,
and the IP Clearance will add a record of the contribution being officially
donated from Adobe for the benefit of any future doubt.

On 12 Sep 2017 12:57 am, "Tobias Bocanegra"  wrote:

Hi Stian,

No :-( I was told, that this is not required for so little code. However, I
will start the IP clearance nevertheless.
Regards, toby


On 12 September 2017 at 08:35:27, Stian Soiland-Reyes (st...@apache.org)
wrote:

Good idea!

Have you already started IP Clearance [1] of the new contribution that was
developed outside ASF?

[1] http://incubator.apache.org/ip-clearance/


Re: Donation of Adobe's content-package-maven-plugin

2017-09-11 Thread Tobias Bocanegra
Hi Stian,

No :-( I was told, that this is not required for so little code. However, I 
will start the IP clearance nevertheless.
Regards, toby



On 12 September 2017 at 08:35:27, Stian Soiland-Reyes 
(st...@apache.org) wrote:

Good idea!

Have you already started IP Clearance [1] of the new contribution that was 
developed outside ASF?

[1] http://incubator.apache.org/ip-clearance/



Re: Donation of Adobe's content-package-maven-plugin

2017-09-11 Thread Stian Soiland-Reyes
Good idea!

Have you already started IP Clearance [1] of the new contribution that was
developed outside ASF?

[1] http://incubator.apache.org/ip-clearance/

On 8 Sep 2017 5:46 am, "Tobias Bocanegra"  wrote:

> Hi devs,
>
> tl;dr:
> I'm about to contribute the content-package-maven-plugin to (jackrabbit)
> filevault. If you have any objections, please bring them forward.
>
> More details:
>
> The content-package maven plugin is a maven plugin that simplifies the
> creation of content package maven artifacts. The content packages can later
> be used to install content into a JCR repository using the Apache
> Jackrabbit FileVault packaging runtime.
>
> Filevault was contributed 4 years ago, but we never had a tool to create
> the packaged during runtime. Adobe's plugin is publicly available, but only
> in binary form. With this contribution, we want to bring the source and
> development closer to the filevault core and to leverage the community
> better in driving this plugin further.
>
> The respective positions in Adobe approved the contribution, I refactored
> the package space and cleaned up the copyrights. All is left to commit it
> somewhere. I plan to put it beside the filevault project at:
> https://svn.apache.org/repos/asf/jackrabbit/commons/package-maven-plugin.
>
> alternatively, we could also request a git repository and only host it
> there. please advice.
>
> more details about the location, java package name, plugin attract name
> can be found here:
> https://issues.apache.org/jira/browse/JCRVLT-202
>
>
> thanks.
> regards, toby
>
>
>
>


Re: Donation of Adobe's content-package-maven-plugin

2017-09-11 Thread Tobias Bocanegra
On 11 September 2017 at 18:57:04, Davide Giannella 
(dav...@apache.org) wrote:
I don't have any specific preferences but I'm wondering that as the main
development effort has moved now to Oak if rather than put it under
jackrabbit it would make more sense to put it under somewhere in Oak.

Hi Davide,

Thanks for your input. FileVault is still called Jackrabbit Filevault, and Oak 
is actually called Jackrabbit Oak [0]. So I rather keep it as a sibling to 
FileVault.

Regards, toby

[0] https://jackrabbit.apache.org/oak/


BUILD FAILURE: Jackrabbit Oak - Build # 728 - Still Failing

2017-09-11 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #728)

Status: Still Failing

Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/728/ to 
view the results.

Changes:
[mreutegg] OAK-6647: Reduce reads by RevisionGC

[tomekr] OAK-6644: Use ReadOnlyNodeBuilder for the read-only mounts

 

Test results:
All tests passed

Re: September report: draft for review

2017-09-11 Thread Cédric Damioli



Le 11/09/2017 à 15:54, Michael Dürig a écrit :


Hi,

I've assembled a preliminary board report for September:

https://wiki.apache.org/jackrabbit/Board%20Report%20September%202017

Please have a look at let me know of any omissions or corrections. I 
plan to submit it next Wednesday morning CET.


Michael



+1

--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org



Re: [VOTE] Release Apache Jackrabbit Oak 1.7.7

2017-09-11 Thread Julian Reschke

On 2017-09-11 15:12, Davide Giannella wrote:

...


The check release script is happy, but running

  mvn clean install -PintegrationTesting

on Windows reliably fails, see OAK-6641 and OAK-6648. I *believe* these 
problems have been present in OAK 1.7.6 already, though.


Best regards, Julian


Re: September report: draft for review

2017-09-11 Thread Robert Munteanu
On Mon, 2017-09-11 at 15:54 +0200, Michael Dürig wrote:
> Hi,
> 
> I've assembled a preliminary board report for September:
> 
> https://wiki.apache.org/jackrabbit/Board%20Report%20September%202017
> 
> Please have a look at let me know of any omissions or corrections. I 
> plan to submit it next Wednesday morning CET.

Looks good, thank you.

Robert


Re: [VOTE] Release Apache Jackrabbit Oak 1.7.7

2017-09-11 Thread Davide Giannella
[X] +1 Release this package as Apache Jackrabbit Oak 1.7.7


BUILD FAILURE: Jackrabbit Oak - Build # 727 - Still Failing

2017-09-11 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #727)

Status: Still Failing

Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/727/ to 
view the results.

Changes:
[tommaso] OAK-6646 - set connection timeouts in Solr index

 

Test results:
1 tests failed.
FAILED:  
org.apache.jackrabbit.oak.jcr.observation.ObservationQueueFullWarnTest.testQueueFullThenFlushing[SegmentTar]

Error Message:
Just filled queue must not convert local->external expected:<6> but was:<4>

Stack Trace:
java.lang.AssertionError: Just filled queue must not convert local->external 
expected:<6> but was:<4>
at 
org.apache.jackrabbit.oak.jcr.observation.ObservationQueueFullWarnTest.testQueueFullThenFlushing(ObservationQueueFullWarnTest.java:312)

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.7

2017-09-11 Thread Andrei Dulceanu
 [X] +1 Release this package as Apache Jackrabbit Oak 1.7.7

2017-09-11 16:12 GMT+03:00 Davide Giannella :

> Please vote on releasing this package as Apache Jackrabbit Oak 1.7.7.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.7
> [ ] -1 Do not release this package because...
>
> D.
>

Regards,
Andrei


Re: September report: draft for review

2017-09-11 Thread Julian Reschke

On 2017-09-11 15:54, Michael Dürig wrote:


Hi,

I've assembled a preliminary board report for September:

https://wiki.apache.org/jackrabbit/Board%20Report%20September%202017

Please have a look at let me know of any omissions or corrections. I 
plan to submit it next Wednesday morning CET.


Michael


LGTM.


September report: draft for review

2017-09-11 Thread Michael Dürig


Hi,

I've assembled a preliminary board report for September:

https://wiki.apache.org/jackrabbit/Board%20Report%20September%202017

Please have a look at let me know of any omissions or corrections. I 
plan to submit it next Wednesday morning CET.


Michael




Re: [VOTE] Release Apache Jackrabbit 2.14.3

2017-09-11 Thread Julian Reschke

On 2017-09-11 15:35, Julian Reschke wrote:

 ...


[X] +1 Release this package as Apache Jackrabbit 2.14.3

Best regards, Julian


BUILD FAILURE: Jackrabbit Oak - Build # 726 - Failure

2017-09-11 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #726)

Status: Failure

Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/726/ to 
view the results.

Changes:
[catholicon] OAK-6544: Enable active blob deletion feature by default

Enable the feature by default with 12 hour interval for execution

 

Test results:
All tests passed

[VOTE] Release Apache Jackrabbit Oak 1.7.7

2017-09-11 Thread Davide Giannella
A candidate for the Jackrabbit Oak 1.7.7 release is available at:

    https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.7.7/

The release candidate is a zip archive of the sources in:

   
https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.7.7/

The SHA1 checksum of the archive is
3d57847b3dbf390daf7c552472fb3a53f63b2558.

A staged Maven repository is available for review at:

    https://repository.apache.org/

The command for running automated checks against this release candidate is:

    $ sh check-release.sh oak 1.7.7 3d57847b3dbf390daf7c552472fb3a53f63b2558

Please vote on releasing this package as Apache Jackrabbit Oak 1.7.7.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.

    [ ] +1 Release this package as Apache Jackrabbit Oak 1.7.7
    [ ] -1 Do not release this package because...

D.


Re: Release process and staging upload

2017-09-11 Thread Julian Reschke

On 2017-09-11 14:47, Davide Giannella wrote:

Hello team,

what are the reasons we're uploading a zip binary of the sources for Oak
to staging and then production? I think most, if not all, of the oak
users leverage maven repositories and the zip is therefore not used.

Can we skip such step, at least for Oak, and drive all the users to use
the maven repos and the svn tags for sources? Are we obliged by any
Apache restriction to provide a zip of the sources?

Cheers
Davide




Best regards, Julian


Release process and staging upload

2017-09-11 Thread Davide Giannella
Hello team,

what are the reasons we're uploading a zip binary of the sources for Oak
to staging and then production? I think most, if not all, of the oak
users leverage maven repositories and the zip is therefore not used.

Can we skip such step, at least for Oak, and drive all the users to use
the maven repos and the svn tags for sources? Are we obliged by any
Apache restriction to provide a zip of the sources?

Cheers
Davide




[jira] [Reopened] (JCRVLT-202) Import Adobe's content package maven plugin

2017-09-11 Thread Tobias Bocanegra (JIRA)

 [ 
https://issues.apache.org/jira/browse/JCRVLT-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tobias Bocanegra reopened JCRVLT-202:
-

[~rombert] that's a good idea. I will rename the plugin.

> Import Adobe's content package maven plugin
> ---
>
> Key: JCRVLT-202
> URL: https://issues.apache.org/jira/browse/JCRVLT-202
> Project: Jackrabbit FileVault
>  Issue Type: Task
>  Components: package maven plugin
>Reporter: Tobias Bocanegra
>Assignee: Tobias Bocanegra
> Fix For: package-maven-plugin-1.0.0
>
>
> The content-package maven plugin is a maven plugin that simplifies the 
> creation of content package maven artifacts. The content packages can later 
> be used to install content into a JCR repository using the Apache Jackrabbit 
> FileVault packaging runtime.
> Filevault was contributed 4 years ago, but we never had a tool to create the 
> packaged during runtime. Adobe's plugin is publicly available, but only in 
> binary form. With this contribution, we want to bring the source and 
> development closer to the filevault core and to leverage the community better 
> in driving this plugin further.
> *details*
> java package space: 
> {code}
> org.apache.jackrabbit.filevault.maven.packaging
> {code}
> plugin name:
> {code}
> org.apache.jackrabbit.filevault
> package-maven-plugin
> {code}
> scm location: 
> - a) SVN: 
> https://svn.apache.org/repos/asf/jackrabbit/commons/package-maven-plugin
> - b) GIT: 
> https://git-wip-us.apache.org/repos/asf?p=jackrabbit-filevault-package-plugin.git;a=tree



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Donation of Adobe's content-package-maven-plugin

2017-09-11 Thread Davide Giannella
Hello Tobi,

On 08/09/2017 05:45, Tobias Bocanegra wrote:
> All is left to commit it somewhere. I plan to put it beside the
> filevault project
> at: https://svn.apache.org/repos/asf/jackrabbit/commons/package-maven-plugin.
>
> alternatively, we could also request a git repository and only host it
> there. please advice.

I don't have any specific preferences but I'm wondering that as the main
development effort has moved now to Oak if rather than put it under
jackrabbit it would make more sense to put it under somewhere in Oak.

D.


Re: Intended to backport OAK-6110 to 1.6

2017-09-11 Thread Andrei Dulceanu
+1

2017-09-11 11:46 GMT+03:00 Davide Giannella :

> On 11/09/2017 09:05, Michael Dürig wrote:
> > I intend to backport OAK-6110 to Oak 1.6. See OAK-6642 for a patch.
> +1
> D.
>


Re: Intended to backport OAK-6110 to 1.6

2017-09-11 Thread Davide Giannella
On 11/09/2017 09:05, Michael Dürig wrote:
> I intend to backport OAK-6110 to Oak 1.6. See OAK-6642 for a patch. 
+1
D.


Intended to backport OAK-6110 to 1.6

2017-09-11 Thread Michael Dürig


Hi,

I intend to backport OAK-6110 to Oak 1.6. See OAK-6642 for a patch.
The fix is very simple and showed big performance and scalability 
improvements compacting repositories with nodes having many siblings.


Michael


[jira] [Commented] (JCRVLT-202) Import Adobe's content package maven plugin

2017-09-11 Thread Robert Munteanu (JIRA)

[ 
https://issues.apache.org/jira/browse/JCRVLT-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160884#comment-16160884
 ] 

Robert Munteanu commented on JCRVLT-202:


A solution that would remove duplication is using 
{{org.apache.jackrabbit:filevault-package-maven-plugin}}.

> Import Adobe's content package maven plugin
> ---
>
> Key: JCRVLT-202
> URL: https://issues.apache.org/jira/browse/JCRVLT-202
> Project: Jackrabbit FileVault
>  Issue Type: Task
>  Components: package maven plugin
>Reporter: Tobias Bocanegra
>Assignee: Tobias Bocanegra
> Fix For: package-maven-plugin-1.0.0
>
>
> The content-package maven plugin is a maven plugin that simplifies the 
> creation of content package maven artifacts. The content packages can later 
> be used to install content into a JCR repository using the Apache Jackrabbit 
> FileVault packaging runtime.
> Filevault was contributed 4 years ago, but we never had a tool to create the 
> packaged during runtime. Adobe's plugin is publicly available, but only in 
> binary form. With this contribution, we want to bring the source and 
> development closer to the filevault core and to leverage the community better 
> in driving this plugin further.
> *details*
> java package space: 
> {code}
> org.apache.jackrabbit.filevault.maven.packaging
> {code}
> plugin name:
> {code}
> org.apache.jackrabbit.filevault
> package-maven-plugin
> {code}
> scm location: 
> - a) SVN: 
> https://svn.apache.org/repos/asf/jackrabbit/commons/package-maven-plugin
> - b) GIT: 
> https://git-wip-us.apache.org/repos/asf?p=jackrabbit-filevault-package-plugin.git;a=tree



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Donation of Adobe's content-package-maven-plugin

2017-09-11 Thread Tobias Bocanegra
Hi,

I committed the initial version here:
https://svn.apache.org/viewvc?view=revision=1807995

I you don’t object, I will announce the donation to the users and announce 
list, in about 24h.
After that, I will try to cut release 1.0.0.

Thanks.
Regards, toby



On 8 September 2017 at 13:45:45, Tobias Bocanegra 
(tri...@adobe.com) wrote:

Hi devs,

tl;dr:
I'm about to contribute the content-package-maven-plugin to (jackrabbit) 
filevault. If you have any objections, please bring them forward.

More details:

The content-package maven plugin is a maven plugin that simplifies the creation 
of content package maven artifacts. The content packages can later be used to 
install content into a JCR repository using the Apache Jackrabbit FileVault 
packaging runtime.

Filevault was contributed 4 years ago, but we never had a tool to create the 
packaged during runtime. Adobe's plugin is publicly available, but only in 
binary form. With this contribution, we want to bring the source and 
development closer to the filevault core and to leverage the community better 
in driving this plugin further.

The respective positions in Adobe approved the contribution, I refactored the 
package space and cleaned up the copyrights. All is left to commit it 
somewhere. I plan to put it beside the filevault project at: 
https://svn.apache.org/repos/asf/jackrabbit/commons/package-maven-plugin.

alternatively, we could also request a git repository and only host it there. 
please advice.

more details about the location, java package name, plugin attract name can be 
found here:
https://issues.apache.org/jira/browse/JCRVLT-202


thanks.
regards, toby





[jira] [Resolved] (JCRVLT-202) Import Adobe's content package maven plugin

2017-09-11 Thread Tobias Bocanegra (JIRA)

 [ 
https://issues.apache.org/jira/browse/JCRVLT-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tobias Bocanegra resolved JCRVLT-202.
-
   Resolution: Fixed
Fix Version/s: package-maven-plugin-1.0.0

> Import Adobe's content package maven plugin
> ---
>
> Key: JCRVLT-202
> URL: https://issues.apache.org/jira/browse/JCRVLT-202
> Project: Jackrabbit FileVault
>  Issue Type: Task
>  Components: package maven plugin
>Reporter: Tobias Bocanegra
>Assignee: Tobias Bocanegra
> Fix For: package-maven-plugin-1.0.0
>
>
> The content-package maven plugin is a maven plugin that simplifies the 
> creation of content package maven artifacts. The content packages can later 
> be used to install content into a JCR repository using the Apache Jackrabbit 
> FileVault packaging runtime.
> Filevault was contributed 4 years ago, but we never had a tool to create the 
> packaged during runtime. Adobe's plugin is publicly available, but only in 
> binary form. With this contribution, we want to bring the source and 
> development closer to the filevault core and to leverage the community better 
> in driving this plugin further.
> *details*
> java package space: 
> {code}
> org.apache.jackrabbit.filevault.maven.packaging
> {code}
> plugin name:
> {code}
> org.apache.jackrabbit.filevault
> package-maven-plugin
> {code}
> scm location: 
> - a) SVN: 
> https://svn.apache.org/repos/asf/jackrabbit/commons/package-maven-plugin
> - b) GIT: 
> https://git-wip-us.apache.org/repos/asf?p=jackrabbit-filevault-package-plugin.git;a=tree



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (JCRVLT-202) Import Adobe's content package maven plugin

2017-09-11 Thread Tobias Bocanegra (JIRA)

[ 
https://issues.apache.org/jira/browse/JCRVLT-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160812#comment-16160812
 ] 

Tobias Bocanegra commented on JCRVLT-202:
-

comitted in r1807995.

https://svn.apache.org/viewvc?view=revision=1807995

> Import Adobe's content package maven plugin
> ---
>
> Key: JCRVLT-202
> URL: https://issues.apache.org/jira/browse/JCRVLT-202
> Project: Jackrabbit FileVault
>  Issue Type: Task
>  Components: package maven plugin
>Reporter: Tobias Bocanegra
>Assignee: Tobias Bocanegra
>
> The content-package maven plugin is a maven plugin that simplifies the 
> creation of content package maven artifacts. The content packages can later 
> be used to install content into a JCR repository using the Apache Jackrabbit 
> FileVault packaging runtime.
> Filevault was contributed 4 years ago, but we never had a tool to create the 
> packaged during runtime. Adobe's plugin is publicly available, but only in 
> binary form. With this contribution, we want to bring the source and 
> development closer to the filevault core and to leverage the community better 
> in driving this plugin further.
> *details*
> java package space: 
> {code}
> org.apache.jackrabbit.filevault.maven.packaging
> {code}
> plugin name:
> {code}
> org.apache.jackrabbit.filevault
> package-maven-plugin
> {code}
> scm location: 
> - a) SVN: 
> https://svn.apache.org/repos/asf/jackrabbit/commons/package-maven-plugin
> - b) GIT: 
> https://git-wip-us.apache.org/repos/asf?p=jackrabbit-filevault-package-plugin.git;a=tree



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)