You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Russell Gold <ru...@oracle.com> on 2019/05/30 12:40:10 UTC

Would it make sense to publish a WAR to maven central?

The open source Weblogic Monitoring Exporter <https://github.com/oracle/weblogic-monitoring-exporter> is a set of servlets that works as an exporter for Prometheus. Building it involves two steps: one build compiles the servlets and the second assembles them into a WAR, in which a configuration file is embedded. Currently, users clone the repository and run both builds, but that means that they generally work with the latest commits. I am thinking that it makes more sense to publish it to maven central, but am looking for guidance. Is it customary to publish WARs to central? In such a case, I would combine the builds, and a simple shell command or script could supply the configuration. Or would it be best to publish the JAR containing the servlets and have users run the second build to create the WAR?

Thanks,
Russ

Re: Would it make sense to publish a WAR to maven central?

Posted by Manfred Moser <ma...@simpligility.com>.
Yes.. publishing war files, executable jar files or install/distribution archives of your app and so on is all within the scope of publishing to Central

Manfred

Matthieu BROUILLARD wrote on 2019-05-30 23:09:

> Why couldn't you publish as a war?
> AFAIK Central is not restricted to be a jar library.
> You can already find wars in central :
> https://search.maven.org/search?q=p:war
> 
> Regards
> 
> Matthieu
> 
> On Thu, May 30, 2019 at 2:40 PM Russell Gold <ru...@oracle.com>
> wrote:
> 
>> The open source Weblogic Monitoring Exporter <
>> https://github.com/oracle/weblogic-monitoring-exporter> is a set of
>> servlets that works as an exporter for Prometheus. Building it involves two
>> steps: one build compiles the servlets and the second assembles them into a
>> WAR, in which a configuration file is embedded. Currently, users clone the
>> repository and run both builds, but that means that they generally work
>> with the latest commits. I am thinking that it makes more sense to publish
>> it to maven central, but am looking for guidance. Is it customary to
>> publish WARs to central? In such a case, I would combine the builds, and a
>> simple shell command or script could supply the configuration. Or would it
>> be best to publish the JAR containing the servlets and have users run the
>> second build to create the WAR?
>>
>> Thanks,
>> Russ
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Would it make sense to publish a WAR to maven central?

Posted by Matthieu BROUILLARD <ma...@brouillard.fr>.
Why couldn't you publish as a war?
AFAIK Central is not restricted to be a jar library.
You can already find wars in central :
https://search.maven.org/search?q=p:war

Regards

Matthieu

On Thu, May 30, 2019 at 2:40 PM Russell Gold <ru...@oracle.com>
wrote:

> The open source Weblogic Monitoring Exporter <
> https://github.com/oracle/weblogic-monitoring-exporter> is a set of
> servlets that works as an exporter for Prometheus. Building it involves two
> steps: one build compiles the servlets and the second assembles them into a
> WAR, in which a configuration file is embedded. Currently, users clone the
> repository and run both builds, but that means that they generally work
> with the latest commits. I am thinking that it makes more sense to publish
> it to maven central, but am looking for guidance. Is it customary to
> publish WARs to central? In such a case, I would combine the builds, and a
> simple shell command or script could supply the configuration. Or would it
> be best to publish the JAR containing the servlets and have users run the
> second build to create the WAR?
>
> Thanks,
> Russ