Hi
You should read the discussion here
https://github.com/eclipse/jetty.project/issues/1527
Cheers
Olivier


On Tue, Nov 13, 2018 at 9:23 PM Filipe Sousa <[email protected]> wrote:

> Hi,
>
> Not sure I understand the problem with the BOM. Adding a parent to the
> jetty-bom like you do with the other modules and use flatten-maven-plugin
> to clean up the BOM should work.
>
> diff --git a/jetty-bom/pom.xml b/jetty-bom/pom.xml
> index abb972743e..0c4beadb73 100644
> --- a/jetty-bom/pom.xml
> +++ b/jetty-bom/pom.xml
> @@ -1,8 +1,11 @@
>  <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
> http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd
> ">
> -  <groupId>org.eclipse.jetty</groupId>
> +  <parent>
> +    <groupId>org.eclipse.jetty</groupId>
> +    <artifactId>jetty-project</artifactId>
> +    <version>9.4.14-SNAPSHOT</version>
> +  </parent>
>    <modelVersion>4.0.0</modelVersion>
>    <artifactId>jetty-bom</artifactId>
> -  <version>9.4.14-SNAPSHOT</version>
>    <name>Jetty :: Bom</name>
>    <description>Jetty BOM artifact</description>
>    <url>http://www.eclipse.org/jetty</url>
> @@ -87,6 +90,40 @@
>          </plugin>
>        </plugins>
>      </pluginManagement>
> +    <plugins>
> +      <plugin>
> +        <groupId>org.codehaus.mojo</groupId>
> +        <artifactId>flatten-maven-plugin</artifactId>
> +        <version>1.0.1</version>
> +        <configuration>
> +          <outputDirectory>${project.build.directory}</outputDirectory>
> +          <flattenedPomFilename>flattened-pom.xml</flattenedPomFilename>
> +          <flattenMode>oss</flattenMode>
> +          <updatePomFile>true</updatePomFile>
> +
>  <embedBuildProfileDependencies>true</embedBuildProfileDependencies>
> +          <pomElements>
> +            <build>remove</build>
> +            <dependencyManagement>keep</dependencyManagement>
> +          </pomElements>
> +        </configuration>
> +        <executions>
> +          <execution>
> +            <id>flatten</id>
> +            <goals>
> +              <goal>flatten</goal>
> +            </goals>
> +            <phase>process-resources</phase>
> +          </execution>
> +          <execution>
> +            <id>flatten.clean</id>
> +            <goals>
> +              <goal>clean</goal>
> +            </goals>
> +            <phase>clean</phase>
> +          </execution>
> +        </executions>
> +      </plugin>
> +    </plugins>
>    </build>
>
>    <dependencyManagement>
>
>
> On 13 Nov 2018, at 00:45, Joakim Erdfelt <[email protected]> wrote:
>
> You are absolutely right, the jetty-bom is missing. :-(
>
> This is because the jetty-bom is a bastard module that is impossible to
> play nice within the maven, all plugins refuse to updates the versions
> within it, as it's not quite within the reactor, nor capable of
> participating within the normal build hierarchy due to the inane rules on
> boms that force this behavior on the rest of the project.
>
> https://github.com/eclipse/jetty.project/blob/jetty-9.4.13.v20181111/jetty-bom/pom.xml#L5
>
> Unfortunately, now that the tag jetty-9.4.13.v20181111 has been created we
> cannot touch that tag (as they are referenced within the jar artifacts
> themselves via both the ref and the commit ids).
> We cannot release jetty-bom using the normal build tools and processes now.
> This will be a manual process, be aware that it can take a while to sort
> out (up to a week).
>
> Joakim Erdfelt / [email protected]
>
> On Mon, Nov 12, 2018 at 5:19 PM Steven Schlansker <
> [email protected]> wrote:
>
>> Hi Joakim,
>>
>> Excited to try Jetty 9.4.13!  However, it seems that the `bom` artifact
>> may have been left behind.
>>
>> According to Maven Central,
>>
>> org.eclipse.jetty
>> Artifact ID
>> jetty-server
>> Latest Version
>> 9.4.13.v20181111
>>
>> org.eclipse.jetty
>> Artifact ID
>> jetty-bom
>> Latest Version
>> 9.4.12.v20180830
>>
>> I apologize if this is due to impatience coupled with inconsistent
>> mirroring delays or some other technical glitch, but it sure looks like the
>> `jetty-bom` artifact may not have been released.
>>
>> > On Nov 12, 2018, at 11:23 AM, Joakim Erdfelt <[email protected]>
>> wrote:
>> >
>> > The Jetty team is happy to announce the immediate availability of a
>> newest release for the Eclipse Jetty 9.4.x branch.
>> > ...
>>
>> _______________________________________________
>> jetty-users mailing list
>> [email protected]
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://www.eclipse.org/mailman/listinfo/jetty-users
>>
> _______________________________________________
> jetty-users mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/jetty-users
>
>
> _______________________________________________
> jetty-users mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/jetty-users



-- 
Olivier
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users

Reply via email to