[jira] [Updated] (MSITE-751) Site generation fails with source directory not foun on multi

2015-11-10 Thread Pedro Vieira Silva (JIRA)

 [ 
https://issues.apache.org/jira/browse/MSITE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pedro Vieira Silva updated MSITE-751:
-
Description: 
When building site for a multimodule project maven site:site fails with the 
following error:

{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-cli) on project 
eclipse: Execution default-cli of goal 
org.apache.maven.plugins:maven-site-plugin:3.4:site failed: Source directory 
'D:\test-project\target\classes' not exists -> [Help 1]
{noformat}

The parent project has packaging pom so it hasn't any target/classes directory 
inside it ...But test-project has several subprojects inside it that in turn 
have packaging type set to jar.

My maven configuration is as follows:

{code:xml}

[...]

  org.apache.maven.plugins
  maven-javadoc-plugin
  2.10.3
  
false
  
  

  aggregate
  
aggregate
  
  site

  

[..]
  

  test-project-site
  My Site
  file:///var/www/html/test-project

  

[...]
{code}


  was:
When building site for a multimodule project maven site:site fails with the 
following error:

{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-cli) on project 
eclipse: Execution default-cli of goal 
org.apache.maven.plugins:maven-site-plugin:3.4:site failed: Source directory 
'D:\test-project\target\classes' not exists -> [Help 1]
{noformat}

The parent project has packaging pom so it hasn't any target/classes directory 
inside it ...But test-project has several subprojects inside it that in turn 
have packaging type set to jar.

My maven configuration is as follows:

{code:xml}

  org.apache.maven.plugins
  maven-javadoc-plugin
  2.10.3
  
false
  
  

  aggregate
  
aggregate
  
  site

  


[..]
  

  test-project-site
  My Site
  file:///var/www/html/test-project

  
{code}



> Site generation fails with  source directory not foun on multi
> --
>
> Key: MSITE-751
> URL: https://issues.apache.org/jira/browse/MSITE-751
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: Maven 3, multi module
>Affects Versions: 3.4
> Environment: Windows 10, JDK8, Maven 3.3.3
>Reporter: Pedro Vieira Silva
>Priority: Blocker
> Fix For: 3.4.1
>
>
> When building site for a multimodule project maven site:site fails with the 
> following error:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-cli) on project 
> eclipse: Execution default-cli of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed: Source directory 
> 'D:\test-project\target\classes' not exists -> [Help 1]
> {noformat}
> The parent project has packaging pom so it hasn't any target/classes 
> directory inside it ...But test-project has several subprojects inside it 
> that in turn have packaging type set to jar.
> My maven configuration is as follows:
> {code:xml}
> [...]
> 
>   org.apache.maven.plugins
>   maven-javadoc-plugin
>   2.10.3
>   
> false
> 
>   
> 
>   aggregate
>   
> aggregate
>   
>   site
> 
>   
> 
> [..]
>   
> 
>   test-project-site
>   My Site
>   file:///var/www/html/test-project
> 
>   
> [...]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (MSITE-751) Site generation fails with source directory not foun on multi

2015-11-10 Thread Pedro Vieira Silva (JIRA)

 [ 
https://issues.apache.org/jira/browse/MSITE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pedro Vieira Silva updated MSITE-751:
-
Description: 
When building site for a multimodule project maven site:site fails with the 
following error:

{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-cli) on project 
eclipse: Execution default-cli of goal 
org.apache.maven.plugins:maven-site-plugin:3.4:site failed: Source directory 
'D:\test-project\target\classes' not exists -> [Help 1]
{noformat}

The parent project has packaging pom so it hasn't any target/classes directory 
inside it ...But test-project has several subprojects inside it that in turn 
have packaging type set to jar.

My maven configuration is as follows:

{code:xml}

[...]

  org.apache.maven.plugins
  maven-site-plugin
  3.4
  

  org.apache.maven.doxia
  doxia-module-markdown
  1.6

  
  
UTF-8
UTF-8
  

[...]

  org.apache.maven.plugins
  maven-javadoc-plugin
  2.10.3
  
false
  
  

  aggregate
  
aggregate
  
  site

  

[..]
  

  test-project-site
  My Site
  file:///var/www/html/test-project

  

[...]
{code}


  was:
When building site for a multimodule project maven site:site fails with the 
following error:

{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-cli) on project 
eclipse: Execution default-cli of goal 
org.apache.maven.plugins:maven-site-plugin:3.4:site failed: Source directory 
'D:\test-project\target\classes' not exists -> [Help 1]
{noformat}

The parent project has packaging pom so it hasn't any target/classes directory 
inside it ...But test-project has several subprojects inside it that in turn 
have packaging type set to jar.

My maven configuration is as follows:

{code:xml}

[...]

  org.apache.maven.plugins
  maven-javadoc-plugin
  2.10.3
  
false
  
  

  aggregate
  
aggregate
  
  site

  

[..]
  

  test-project-site
  My Site
  file:///var/www/html/test-project

  

[...]
{code}



> Site generation fails with  source directory not foun on multi
> --
>
> Key: MSITE-751
> URL: https://issues.apache.org/jira/browse/MSITE-751
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: Maven 3, multi module
>Affects Versions: 3.4
> Environment: Windows 10, JDK8, Maven 3.3.3
>Reporter: Pedro Vieira Silva
>Priority: Blocker
> Fix For: 3.4.1
>
>
> When building site for a multimodule project maven site:site fails with the 
> following error:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-cli) on project 
> eclipse: Execution default-cli of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed: Source directory 
> 'D:\test-project\target\classes' not exists -> [Help 1]
> {noformat}
> The parent project has packaging pom so it hasn't any target/classes 
> directory inside it ...But test-project has several subprojects inside it 
> that in turn have packaging type set to jar.
> My maven configuration is as follows:
> {code:xml}
> [...]
> 
>   org.apache.maven.plugins
>   maven-site-plugin
>   3.4
>   
> 
>   org.apache.maven.doxia
>   doxia-module-markdown
>   1.6
> 
>   
>   
> UTF-8
> UTF-8
>   
> 
> [...]
> 
>   org.apache.maven.plugins
>   maven-javadoc-plugin
>   2.10.3
>   
> false
> 
>   
> 
>   aggregate
>   
> aggregate
>   
>   site
> 
>   
> 
> [..]
>   
> 
>   test-project-site
>   My Site
>   file:///var/www/html/test-project
> 
>   
> [...]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (MSITE-751) Site generation fails with source directory not found on multimodule project

2015-11-10 Thread Pedro Vieira Silva (JIRA)

 [ 
https://issues.apache.org/jira/browse/MSITE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pedro Vieira Silva updated MSITE-751:
-
Summary: Site generation fails with  source directory not found on 
multimodule project  (was: Site generation fails with  source directory not 
foun on multi)

> Site generation fails with  source directory not found on multimodule project
> -
>
> Key: MSITE-751
> URL: https://issues.apache.org/jira/browse/MSITE-751
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: Maven 3, multi module
>Affects Versions: 3.4
> Environment: Windows 10, JDK8, Maven 3.3.3
>Reporter: Pedro Vieira Silva
>Priority: Blocker
> Fix For: 3.4.1
>
>
> When building site for a multimodule project maven site:site fails with the 
> following error:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-cli) on project 
> eclipse: Execution default-cli of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed: Source directory 
> 'D:\test-project\target\classes' not exists -> [Help 1]
> {noformat}
> The parent project has packaging pom so it hasn't any target/classes 
> directory inside it ...But test-project has several subprojects inside it 
> that in turn have packaging type set to jar.
> My maven configuration is as follows:
> {code:xml}
> [...]
> 
>   org.apache.maven.plugins
>   maven-site-plugin
>   3.4
>   
> 
>   org.apache.maven.doxia
>   doxia-module-markdown
>   1.6
> 
>   
>   
> UTF-8
> UTF-8
>   
> 
> [...]
> 
>   org.apache.maven.plugins
>   maven-javadoc-plugin
>   2.10.3
>   
> false
> 
>   
> 
>   aggregate
>   
> aggregate
>   
>   site
> 
>   
> 
> [..]
>   
> 
>   test-project-site
>   My Site
>   file:///var/www/html/test-project
> 
>   
> [...]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (MSITE-751) Site generation fails with source directory not foun on multi

2015-11-10 Thread Pedro Vieira Silva (JIRA)
Pedro Vieira Silva created MSITE-751:


 Summary: Site generation fails with  source directory not foun on 
multi
 Key: MSITE-751
 URL: https://issues.apache.org/jira/browse/MSITE-751
 Project: Maven Site Plugin
  Issue Type: Bug
  Components: Maven 3, multi module
Affects Versions: 3.4
 Environment: Windows 10, JDK8, Maven 3.3.3
Reporter: Pedro Vieira Silva
Priority: Blocker
 Fix For: 3.4.1


When building site for a multimodule project maven site:site fails with the 
following error:

{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-cli) on project 
eclipse: Execution default-cli of goal 
org.apache.maven.plugins:maven-site-plugin:3.4:site failed: Source directory 
'D:\test-project\target\classes' not exists -> [Help 1]
{noformat}

The parent project has packaging pom so it hasn't any target/classes directory 
inside it ...But test-project has several subprojects inside it that in turn 
have packaging type set to jar.

My maven configuration is as follows:

{code:xml}

  org.apache.maven.plugins
  maven-javadoc-plugin
  2.10.3
  
false
  
  

  aggregate
  
aggregate
  
  site

  


[..]
  

  test-project-site
  My Site
  file:///var/www/html/test-project

  
{code}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (MNG-5928) MBP excludes only one package from inlined embeded dependency

2015-11-10 Thread Damyan (JIRA)

 [ 
https://issues.apache.org/jira/browse/MNG-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Damyan updated MNG-5928:

Attachment: pom.xml

> MBP excludes only one package from inlined embeded dependency
> -
>
> Key: MNG-5928
> URL: https://issues.apache.org/jira/browse/MNG-5928
> Project: Maven
>  Issue Type: Bug
>  Components: Embedding
>Affects Versions: 3.2.1
> Environment: Windows 7, Java version: 1.7.0_71
>Reporter: Damyan
> Attachments: pom.xml
>
>
> Working:
> 
>   ;inline=!
> 
> Not working:
> 
>   ;inline=!|
> 
> Also not working when excluding package but inlining others packages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MNG-5928) MBP excludes only one package from inlined embeded dependency

2015-11-10 Thread Damyan (JIRA)

[ 
https://issues.apache.org/jira/browse/MNG-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998230#comment-14998230
 ] 

Damyan commented on MNG-5928:
-

I have added an attachment to the issue. The intention is to repack the embeded 
dependency without several packages (in this case: javax.* and 
org.glassfish.jersey.client.*).

> MBP excludes only one package from inlined embeded dependency
> -
>
> Key: MNG-5928
> URL: https://issues.apache.org/jira/browse/MNG-5928
> Project: Maven
>  Issue Type: Bug
>  Components: Embedding
>Affects Versions: 3.2.1
> Environment: Windows 7, Java version: 1.7.0_71
>Reporter: Damyan
> Attachments: pom.xml
>
>
> Working:
> 
>   ;inline=!
> 
> Not working:
> 
>   ;inline=!|
> 
> Also not working when excluding package but inlining others packages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)