[VOTE] Versioning plugin 0.2.0

2014-05-19 Thread Daniel Kulp

This is a vote to release 0.2.0 of the versioning plugin.

The main change for this plugin is to support both Maven 3.0.x and 3.1.x/3.2.x 
by flipping from using Aether directly to using the Maven provided API’s.   
When released and rolled out throughout the rest of the build, we should 
hopefully be able to build Aries with a more modern version of Maven.


Tag:
https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.versioning-0.2.0/

Staging repo:
https://repository.apache.org/content/repositories/orgapachearies-1000/org/apache/aries/versioning/



-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com



[GitHub] aries pull request: [ARIES-1006] Full compilation support with JDK...

2014-05-19 Thread jbonofre
GitHub user jbonofre opened a pull request:

https://github.com/apache/aries/pull/13

[ARIES-1006] Full compilation support with JDK 7

Patch to fully support compilation with JDK 7

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbonofre/aries ARIES-1006

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/13.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #13


commit 58c28575d2f030ae848805796d357becbe760db9
Author: Jean-Baptiste Onofré jbono...@apache.org
Date:   2014-05-19T19:35:21Z

[ARIES-1006] Full compilation support with JDK 7




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (ARIES-1006) Compilation error with JDK7

2014-05-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/ARIES-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002221#comment-14002221
 ] 

ASF GitHub Bot commented on ARIES-1006:
---

GitHub user jbonofre opened a pull request:

https://github.com/apache/aries/pull/13

[ARIES-1006] Full compilation support with JDK 7

Patch to fully support compilation with JDK 7

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbonofre/aries ARIES-1006

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/13.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #13


commit 58c28575d2f030ae848805796d357becbe760db9
Author: Jean-Baptiste Onofré jbono...@apache.org
Date:   2014-05-19T19:35:21Z

[ARIES-1006] Full compilation support with JDK 7




 Compilation error with JDK7
 ---

 Key: ARIES-1006
 URL: https://issues.apache.org/jira/browse/ARIES-1006
 Project: Aries
  Issue Type: Bug
Reporter: Jean-Baptiste Onofré
Assignee: Timothy Ward
 Attachments: ARIES-1006.patch


 When I try to compile Aries with JDK 7, I have:
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile 
 (default-compile) on project org.apache.aries.testsupport.unit: Compilation 
 failure: Compilation failure:
 [ERROR] could not parse error message: warning: [options] bootstrap class 
 path not set in conjunction with -source 1.5
 [ERROR] 
 /home/jbonofre/workspace/aries/testsupport/testsupport-unit/src/main/java/org/apache/aries/mocks/BundleMock.java:187:
  warning: [deprecation] toURL() in File has been deprecated
 [ERROR] this(name,properties,location.toURL().toExternalForm());
 [ERROR] ^
 [ERROR] 
 [ERROR] 
 /home/jbonofre/workspace/aries/testsupport/testsupport-unit/src/main/java/org/apache/aries/mocks/BundleMock.java:[239,17]
  [deprecation] toURL() in File has been deprecated
 [ERROR] 
 [ERROR] 
 /home/jbonofre/workspace/aries/testsupport/testsupport-unit/src/main/java/org/apache/aries/mocks/BundleMock.java:[263,60]
  [deprecation] toURL() in File has been deprecated
 [ERROR] 
 [ERROR] 
 /home/jbonofre/workspace/aries/testsupport/testsupport-unit/src/main/java/org/apache/aries/mocks/BundleMock.java:[328,65]
  [deprecation] toURL() in File has been deprecated
 [ERROR] 
 It's due to some parent POM definition which force JDK5 support (target and 
 source).
 I don't think that the JDK5 support is still required. I gonna prepare a 
 couple of patches about that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[GitHub] aries pull request: ARIES-1177 Upgrade to Apache POM 14

2014-05-19 Thread jbonofre
GitHub user jbonofre opened a pull request:

https://github.com/apache/aries/pull/14

ARIES-1177 Upgrade to Apache POM 14



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbonofre/aries ARIES-1177

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/14.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #14


commit 3c9a39514a90aa0ef7a815fc0c0a1f0ef6b5f9a2
Author: Jean-Baptiste Onofré jbono...@apache.org
Date:   2014-05-19T19:43:09Z

ARIES-1177 Upgrade to Apache POM 14




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (ARIES-1178) Upgrade to maven-plugin-plugin 3.2

2014-05-19 Thread JIRA

[ 
https://issues.apache.org/jira/browse/ARIES-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002241#comment-14002241
 ] 

Jean-Baptiste Onofré commented on ARIES-1178:
-

[~dkulp] applied the patch as part of the new versioning-plugin release.

 Upgrade to maven-plugin-plugin 3.2
 --

 Key: ARIES-1178
 URL: https://issues.apache.org/jira/browse/ARIES-1178
 Project: Aries
  Issue Type: Bug
Reporter: Jean-Baptiste Onofré
 Attachments: ARIES-1178.patch


 The versioning-plugin currently uses the maven-plugin-plugin 2.3.
 This old version of maven-plugin-plugin still references the old Central 
 URL.
 In order to fix that, we should update to maven-plugin-plugin 3.2.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (ARIES-1178) Upgrade to maven-plugin-plugin 3.2

2014-05-19 Thread JIRA

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

Jean-Baptiste Onofré resolved ARIES-1178.
-

Resolution: Fixed

 Upgrade to maven-plugin-plugin 3.2
 --

 Key: ARIES-1178
 URL: https://issues.apache.org/jira/browse/ARIES-1178
 Project: Aries
  Issue Type: Bug
Reporter: Jean-Baptiste Onofré
 Attachments: ARIES-1178.patch


 The versioning-plugin currently uses the maven-plugin-plugin 2.3.
 This old version of maven-plugin-plugin still references the old Central 
 URL.
 In order to fix that, we should update to maven-plugin-plugin 3.2.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


Re: [VOTE] Versioning plugin 0.2.0

2014-05-19 Thread Sergey Beryozkin

+1

Cheers, Sergey
On 19/05/14 18:15, Daniel Kulp wrote:


This is a vote to release 0.2.0 of the versioning plugin.

The main change for this plugin is to support both Maven 3.0.x and 3.1.x/3.2.x 
by flipping from using Aether directly to using the Maven provided API’s.   
When released and rolled out throughout the rest of the build, we should 
hopefully be able to build Aries with a more modern version of Maven.


Tag:
https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.versioning-0.2.0/

Staging repo:
https://repository.apache.org/content/repositories/orgapachearies-1000/org/apache/aries/versioning/








[jira] [Updated] (ARIES-1187) Installing a subsystem does not cleanup files left in tmp area

2014-05-19 Thread Samuel Bratton (JIRA)

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

Samuel Bratton updated ARIES-1187:
--

Attachment: sbratton_ARIES_1191.patch

Proposed fix: close temp file after InstallAction completes. After the 
subsystem is installed, references to temp zip stick around in installable 
content on the SubSystemResoure. So need to avoid processing them on subsequent 
install calls when not in the context of installing the subsystem. 

 Installing a subsystem does not cleanup files left in tmp area
 --

 Key: ARIES-1187
 URL: https://issues.apache.org/jira/browse/ARIES-1187
 Project: Aries
  Issue Type: Bug
  Components: Subsystem
Affects Versions: subsystem-1.0.1
Reporter: Samuel Bratton
Priority: Minor
 Attachments: sbratton_ARIES_1191.patch


 Installing a subsystem from an esa will leave a file in the temp area with a 
 name like inputStreamExtract296108253125408467.zip



--
This message was sent by Atlassian JIRA
(v6.2#6252)