Weird... I can't replicate it... Dropping it for now.
On Tue, Feb 28, 2017 at 5:34 AM, Paul Merlin wrote:
> Niclas Hedhman a écrit :
> > Somewhere, artifact/version/filename parsing is happening. If I provide a
> > "-Dversion=3.0.0-alpha1" then the file names are screwed up, and becomes
> > ".ja
Niclas Hedhman a écrit :
> Somewhere, artifact/version/filename parsing is happening. If I provide a
> "-Dversion=3.0.0-alpha1" then the file names are screwed up, and becomes
> ".jar", "-sources.jar" and so on, without a name.
>
> The following from a quick test;
>
> 3.0.0 --> correct file names
>
Le 2017-02-26 14:26, Niclas Hedhman a écrit :
* POM has correct artifactId
* $HOME/.m2/repository/ is populated
Cool
* The test/ are still causing issue in IDEA, most likely related to
perfRuntimeOnly configuration that can't be resolved to something
useful.
I don't see any red in IDEA, s
That said;
Somewhere, artifact/version/filename parsing is happening. If I provide a
"-Dversion=3.0.0-alpha1" then the file names are screwed up, and becomes
".jar", "-sources.jar" and so on, without a name.
The following from a quick test;
3.0.0 --> correct file names
3.0.0.alpha1 --> corrupt
3
* POM has correct artifactId
* $HOME/.m2/repository/ is populated
* The test/ are still causing issue in IDEA, most likely related to
perfRuntimeOnly configuration that can't be resolved to something useful.
Cheers
On Sat, Feb 25, 2017 at 7:37 PM, Paul Merlin wrote:
> Niclas,
>
> I just push
Niclas,
I just pushed a fix to the build system for Maven artifactId of
published bits.
`./gradlew install` should now do what you expect.
Could you confirm it works for you?
By the way, I upgraded Gradle to the latest stable release 3.4, enabled
incremental Java compilation and applied the new j
I have been digging in this for a while now, and my findings are...
Since the project.name isn't changed "upfront", but trying to keep the
directory naming, there is a "PublishNaming.publishedNameFor( project.path )"
that tries to set the jar names where needed.
Bizarre enough, the POM generation
Le 12 février 2017 10:25:33 GMT-05:00, Niclas Hedhman a
écrit :
>No 'publishToMavenLocal' task in 'develop' at the moment. Perhaps you
>didn't push it, or...?
>
>
>
>niclas@devdesk:~/dev/polygene/java$ ./gradlew tasks
>:buildSrc:compileJava UP-TO-DATE
>:buildSrc:compileGroovy UP-TO-DATE
>:buildSr
No 'publishToMavenLocal' task in 'develop' at the moment. Perhaps you
didn't push it, or...?
niclas@devdesk:~/dev/polygene/java$ ./gradlew tasks
:buildSrc:compileJava UP-TO-DATE
:buildSrc:compileGroovy UP-TO-DATE
:buildSrc:processResources UP-TO-DATE
:buildSrc:classes UP-TO-DATE
:buildSrc:jar UP
Le 12 février 2017 04:31:44 GMT-05:00, Niclas Hedhman a
écrit :
>I build a distirbution and found a Maven repository inside
>distributions/build/stage
>
>And far more disturbing than not getting .m2/ populated is that the
>produced POMs are invalid. The naming of jar files is messed up now,
>miss
I build a distirbution and found a Maven repository inside
distributions/build/stage
And far more disturbing than not getting .m2/ populated is that the
produced POMs are invalid. The naming of jar files is messed up now,
missing the group in the artifactId.
org.apache.polygene.core
11 matches
Mail list logo
