Hi Robert
I will check out the build with Java 11 and then try to run it under Ubuntu in
a VM.
I will pull the plug on the release as I agree that a build must work but I was
not aware that the build failed until you pointed it out.
Keep you posted - Andy
> On Jan 9, 2020, at 2:04 AM, Robert
On Wed, 2020-01-08 at 07:55 -0800, Andreas Schaefer wrote:
> If a subsequent build works it would mean that in the 2nd build it
> would find the dependency on *.core but not in the first.
>
> This is my env:
>
> mvn --version
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-
If a subsequent build works it would mean that in the 2nd build it would find
the dependency on *.core but not in the first.
This is my env:
mvn --version
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
2019-04-04T12:00:29-07:00)
Maven home: /Java/maven3
Java version: 1.8.0_201,
On Tue, 2020-01-07 at 07:43 -0800, Andreas Schaefer wrote:
> I copied away my ~/.m2/repository and rebuilt the Maven Plugin and
> had no issues whatsoever.
Hm, that is weird. A fresh build of master fails for me:
[INFO] -
[INFO] Build Summary:
[INFO
I copied away my ~/.m2/repository and rebuilt the Maven Plugin and had no
issues whatsoever.
- Andy
> On Jan 6, 2020, at 12:49 PM, Robert Munteanu wrote:
>
> Hi,
>
> On Mon, 2020-01-06 at 09:13 -0800, Andreas Schaefer wrote:
>> Hi Robert
>>
>> All the IT tests are failing because the ‘core’
Hi,
On Mon, 2020-01-06 at 09:13 -0800, Andreas Schaefer wrote:
> Hi Robert
>
> All the IT tests are failing because the ‘core’ artifact is not
> installed locally. The invoker goals are set to ‘clean install’ but
> for the core that seems not to be applied. When I test it locally the
> core artif
Hi Robert
All the IT tests are failing because the ‘core’ artifact is not installed
locally. The invoker goals are set to ‘clean install’ but for the core that
seems not to be applied. When I test it locally the core artifact (both POM and
the JAR file) are installed in the local maven repo.
T
Hi Andy,
On Fri, 2019-12-20 at 16:17 -0800, Andreas Schaefer wrote:
> This is the initial release of the Sling Feature Model Converter
> Plugin
(snip)
The build seems to consistently fail on Jenkins
https://builds.apache.org/blue/organizations/jenkins/Sling%2Fsling-feature-converter-maven-pl
+1 (checked signatures and build)
Georg
On 2019-12-21 01:17, Andreas Schaefer wrote:
Hi,
This is the initial release of the Sling Feature Model Converter
Plugin that is the Maven frontend to the Content Package Converter
module allowing a developer to convert its CP module into a Feature
Model
Hi,
This is the initial release of the Sling Feature Model Converter Plugin that is
the Maven frontend to the Content Package Converter module allowing a developer
to convert its CP module into a Feature Model to be used later in a Feature
Launch.
We solved 2 issues in this release:
https://is
10 matches
Mail list logo
