[ 
https://issues.apache.org/jira/browse/PLC4X-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17030395#comment-17030395
 ] 

Jens Vagts edited comment on PLC4X-173 at 2/5/20 6:59 AM:
----------------------------------------------------------

Yes you are right: source artifacts are provided for the release versions as 
listed on maven central: 
[org/apache/plc4x/plc4j-api/0.5.0|https://repo1.maven.org/maven2/org/apache/plc4x/plc4j-api/0.5.0/].
Just figured out or own remote repo (Nexus) seems to be the cause. Without 
using our repo server the Eclipse m2e maven tooling is able to download the 
sources.

Sorry [~cdutz] for the mistake, just learning you great library, but should 
know maven better! I'm closing this issue right now.


was (Author: vagtsi):
Yes you are right: source artifacts are provided for the release versions as 
listed on maven central: 
[org/apache/plc4x/plc4j-api/0.5.0|https://repo1.maven.org/maven2/org/apache/plc4x/plc4j-api/0.5.0/].
Just figured out or own remote repo (Nexus) seems to be the cause. Without 
using our repo server the Eclipse m2e maven tooling is able to download the 
sources.

Sorry [~cdutz] for the mistake, just learning you great library, but should now 
maven better! I'm closing this issue right now.

> Provide source code artifacts for all java binary artifacts
> -----------------------------------------------------------
>
>                 Key: PLC4X-173
>                 URL: https://issues.apache.org/jira/browse/PLC4X-173
>             Project: Apache PLC4X
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 0.7.0
>            Reporter: Jens Vagts
>            Assignee: Christofer Dutz
>            Priority: Major
>
> For debugging into the PLC4J library source code it would be very convenient 
> to be able to download the appropriate source code artifacts from the public 
> maven repository.
> The required maven plugin _maven-source-plugin_ is already configured within 
> the parent maven pom but not assigned to the module builds, so would be a 
> quite easy fix :)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to