I've created http://jira.codehaus.org/browse/MAVENUPLOAD-802
and attached POMs for com.sun:rt:1.3.1_08 / 1.4.1_06 / 1.5.0_06
dan tran a écrit :
please do create standard pom.
-D
On 3/28/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
I would say com.sun
Also if you want to make poms i'm
wonder if it makes more sense to name the group com.sun.jre?
-D
On 3/29/06, Nicolas De Loof [EMAIL PROTECTED] wrote:
I've created http://jira.codehaus.org/browse/MAVENUPLOAD-802
and attached POMs for com.sun:rt:1.3.1_08 / 1.4.1_06 / 1.5.0_06
dan tran a écrit :
please do create standard
I'd like to add JRE rt.jar as a dependency to my POM, so that I can
use it in compiler plugin configuration :
bootclasspath${pom.getDependencyPath('jara:rt')}/bootclasspath
As this jar should be devivered on the system, I've set scope to system :
dependency
groupIdjava/groupId
systemPath${java.home}/../rt.jar/systemPath
That's how it's supposed to work.
in my opinion it'd probably be better in the repository also, but
anyway it's not redistributable.
On 3/29/06, Nicolas De Loof [EMAIL PROTECTED] wrote:
I'd like to add JRE rt.jar as a dependency to my POM, so that I
I also have considered adding it to my private repository.
Would you consider using java groupId a good practice (according to
SUN jar conventions), or may I use com.sun to put SUN JRE jars
in my repo ?
Carlos Sanchez a écrit :
systemPath${java.home}/../rt.jar/systemPath
That's how it's
please do create standard pom.
-D
On 3/28/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
I would say com.sun
Also if you want to make poms i'm open to put them in ibiblio for
better consistency.
On 3/29/06, Nicolas De Loof [EMAIL PROTECTED] wrote:
I also have considered adding it to my
